Open topic with left hand navigation
Proliance provides fine-grained control over who can access, view and change various aspects of the application. You can allow and restrict user access for:
Proliance uses a role-based security model. Each role has a set of permissions that you can enable or disable for features and documents. Permission settings pages are made available according to a security hierarchy composed of:
Licensing. Access to specific Proliance Work Areas (Portfolios, Workspaces) is controlled via Meridian licensing.
Security or Company Role. Proliance uses two types of roles, security roles and company roles. Company roles are automatically applied to users who are associated with a particular company, while security roles permissions can apply more generally. For more information about roles, see "About Security Roles". For more information about role permissions and their availability in different configurations and work areas, see "About Security Permissions".
Work Area. You can modify permissions at each of the Org, Portfolio and Workspace work area levels. Security permissions that are available within roles vary according to the work area level.
User account settings. Accounts identify users to Proliance and can enable them to log on to a work area. For more information, see "About Accounts".
Projects. You can restrict access to project-related documents based on a contact's link to that project and their Project Team Role. For more information, see " Project Security".
Documents Settings. Using Proliance Local Admin, you can indicate which roles have access to a specific document subtype. For more information, see "About Document Subtypes". Any document created from a document subtype is a document instance. Your permission to a document instance is determined by your company. If your company has permission to a document instance, you will have the same permission. For more information, see "About Document Instances".