System Permissions

Systems permissions are those that allow or deny users or roles the ability to use certain features and functions of the application, documents, templates, and integrated web services, and limit the information seen by members of partner organizations. System permissions are managed in the User Properties or Roles Properties dialog boxes. These dialog boxes display when you create or edit a new user or role in the Administration > Users & Roles > Users or Administration > Users & Roles > Roles workspaces.

For more information, on granting permissions to users or roles, see Add or edit a user and Add or edit a role.

Note: To search this topic for a specific permissions or related functions, click the expand button Expand Collapse button to expand all dropdowns and press either Ctrl+F (PC users) or Command + F (Mac users) to bring up a search tool.

Application Permissions

The list of application permissions below includes a description of the permission, along with the page or function where a user will perform actions that are affected by that permission.

Administration

Architecting

AI Assist

General

Library

Some of the permissions below grant the user permission to perform an action on a folder or its content without specifically assigning permissions on that folder or content record. When granted, those permissions affect all folders and contents in the library, regardless of folder and content level settings.

Caution: Do not enable Library permissions related to viewing, editing, managing or submitting content if you have permissions set at the content or folder level. These permissions will override those permissions.

Permission Sets

Project Documents (Related Files)

Projects

ProSearch

Reports

Document Type Permissions

Document Type permissions control the document types that a selected user or role can use to build, edit, and architect. Verify the Manage Document Types Application Permission is enabled before selecting document types for use if the users will be given Architect permission. Document Type permissions can also be granted to users or roles on the Architecting > Document Type Properties page.

  • Build: Grants the selected user or role the permission to use the document type to build a document.
  • Edit: This is an inactive legacy permission.
  • Architect: Grants the selected user or role the permission to design a document type.

Template Permissions

Selecting the check box in the Enable column grants the selected user or role the permission to use the template when working with content. If a template is enabled for document type, it must also be enabled for the user or role in order for user to apply on the Build tab. These permissions also control which style templates are available from the Qvidian toolbar in Word.

Integration Permissions

Extension Web Service Actions that have been previously configured are displayed in the Integration Permissions panel. You can enable the Actions for the Extension Web Services System that the selected User can call on specified Upland Qvidian Data and Selection Screens. The Integration Tab only displays when a Upland Qvidian Business Logic Web Service has been defined in the web.config file for operation and use. This panel displays the Extension Web Service Actions previously configured.

  • Enable: Enables one permission for an External System.
  • Enable All: Enables all Permissions for all External Systems.
  • Disable All: Disables all Permissions for all External Systems.
  • Enable Selected: Enables all Permissions for all selected External Systems.
  • Disable Selected: Disables all Permissions for all selected External Systems.

Partner Permissions

Partner permissions limit the information resellers, also known as channel partners, can see in their projects, created documents, and the library. In projects and created documents, users with partner permissions can only see participants within their partner group. In the library, they will only see their group's project usage under Content Usage. They will be able to see the Created By, Last Modified By or Last Used By information in the Additional Details tab in the properties of a content record, regardless of whether that user was included in their of the user's organization. When this permission is added to a role, the role and the partner organization associated with it displays in the user's User Properties in Partner Permissions panel.

  • To add a partner permission, enter the partner name(s) in the appropriate field. Multiple partner names should be separated with a (;) semi colon.

Note: Depending on their permissions, participants may be able to view other partner groups' participant and activity information in other areas of Upland Qvidian. Please use caution when assigning permissions to users with partner permissions.