Previous Page | Next Page

Checklists

Who's Who in the SAS Metadata

Main SAS Identities
SAS User, Group, or Role Description1
[user]SAS Administrator A predefined super user that has unrestricted access in the metadata layer.
[user]SAS Demo User A predefined first user that can be useful for demonstrations.
[user]SAS Trusted User A service identity that can act on behalf of other users.
[user]SAS Anonymous Web User A service identity that can provide anonymous access for a few Web components.2
[group]SAS General Servers A service group that enables its member (the SAS Trusted User) to see server launch credentials.3
[group]SAS System Services A service group that enables its member (the SAS Trusted User) to see servers, cubes, and other objects.
[group]PUBLIC Everyone who can access the metadata server. A PUBLIC-only user can't use the deployment.
[group]SASUSERS Everyone who has a well-formed user definition. The subset of PUBLIC that can use the deployment.
[group]SAS Administrators General metadata administrators. Membership in this group provides broad access to metadata, but doesn't provide unrestricted access.
[role]Metadata Server: Unrestricted A highly privileged role that provides unrestricted access in the metadata layer.
[role]Metadata Server: User Administration A role that enables members ( [group]SAS Administrators) to manage most users, groups, and roles, but doesn't provide visibility for any plug-in.
[role]Metadata Server: Operation A role that enables members ( [group]SAS Administrators) to perform most server administration activities, but doesn't provide visibility for any plug-in.
[role]Management Console: Advanced A role that enables members ( [group]SAS Administrators) to see all SAS Management Console plug-ins.
[role]Management Console: Content Management A role that enables members ( [group]SASUSERS) to see a subset of SAS Management Console plug-ins.
1 Descriptions reflect the initial configuration in a new deployment. You can choose to redistribute privileges in a more or less granular approach.

2 For only SAS BI Web Services and the SAS Stored Processes application. Not for other Web applications such as SAS Web Report Studio. Anonymous access is an optional feature that is not compatible with Web authentication.

3 Server launch credentials (for example, the SAS Spawned Servers account, sassrv) are stored in logins on the Accounts tab of the SAS General Servers group. This facilitates launching of stored process servers and pooled workspace servers.

See Also

Launch Credentials

Roles Overview

Main Administrative Roles

Differences Between Roles and Groups

About PUBLIC Access and Anonymous Access

Overview of Initial Roles, Groups, and Users in the SAS Intelligence Platform: System Administration Guide

The administrative documentation for your applications (for application-specific predefined groups and roles)

Previous Page | Next Page | Top of Page