Architect security enables a system administrator to control which projects and global library volumes a user may access, and what privileges that user has within those environments. Permissions are granted to individual users, or to new objects called Security Groups. A user registered into one or more of these security groups inherits all the privileges assigned to those security groups.
The administrator defines the following security configurations in the Configuration module:
Define Security Roles for Architect Project and Architect Global Library and assign Actions to them
Manage Security Groups - edit existing ones or add new ones
Grant security groups access to specific projects or volumes based on a security role (for example, any user in Global Library Group A with a Global Library Role A can be given privileges on Global Library Volume Library 1).
Similarly, a user administrator can set up the following user security in the User Administration module:
Set up the user's security role assignments - grant or deny users access to specific projects or volumes based on a security role
Manage users in each security group - remove users from a group, search for new users to add to the group
View a user's permissions derived from the user's roles and security groups - whether assigned directly to the user, or indirectly via the user's group affiliation.
If a user is assigned to an Architect Project or Global Library Role that has no permissions set or if the user is assigned directly or indirectly through a security group to an only role in the group that has no permissions set, the system will deny the user access to the Architect Projects and Global Library Volumes and display an error message.
Based on permissions that are granted to the user's Architect Group (s), certain features in Architect will not be available to users. To learn more about the user's Project and Global Library Volume permissions, see Related Topics.
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.