Overview of Security

Go Up to Administrator Guide

To log in to ER/Studio Team Server you need both a valid user connection and a valid user account.

User connections determine the user sessions that ER/Studio Team Server can host, and the type of user experience of each one of those sessions. You can purchase licenses for different number of user connections (Platinum, Gold, Silver and Bronze Edition), and register these licenses in ER/Studio Team Server to enable your user connections.

User accounts and user roles are not defined within ER/Studio Team Server itself. To log in to ER/Studio Team Server, you must use the credentials of an ER/Studio Repository user account or, if you configure ER/Studio Team Server to support LDAP, the credentials of an LDAP user account.

Note: To log in to ER/Studio Team Server with ER/Studio Repository user accounts, you must synchronize ER/Studio Team Server with ER/Studio Repository first.

When you first log in to ER/Studio Team Server, the authentication process assigns you a user experience based on the available user connections and the access control permissions group defined by default. Depending on your user experience, ER/Studio Team Server provides a different user interface with access to a different set of features.

Once you are logged in, your user account, roles, and access control permissions determine what content of ER/Studio Team Server you can access and which actions you can perform. Some of those restrictions come from ER/Studio Repository, other restrictions are specific to ER/Studio Team Server and super users can configure them in ER/Studio Team Server.

When you create resources in ER/Studio Team Server (glossaries, terms, or data sources), you become their author. Only authors, super users and stewards can edit those resources and add or remove stewards from them. This does not apply to Reader licenses as the read-only license cannot be assigned as Steward. Nor create, modify, or delete Team Server objects. To change an Author licensed user to a Reader, they can not be a current Steward of any resources.

If you configure ER/Studio Team Server to work with Microsoft SQL Server as the database platform for the Reporting Repository database, ER/Studio Team Server offers the facility to enable encryption of all communications between ER/Studio Team Server and the Reporting Repository.

Topics

• Overview:
  • Connection Licenses
  • User Accounts
  • User Authentication
  • User Experiences
  • User Roles
  • User Permissions
  • Stewards
• Access Control Permissions
• Enabling Secure HTTP Connections
• Modifying the User Session Idle Time Limit
• Tracking User Activity

See Also

• Quick Start Guide: Log In to ER/Studio Team Server
• Overview of the ER/Studio Team Server Architecture
• Overview of Data Synchronization