Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

User Permissions

Warning: Session variables versus fields from the CRM quote context.

As a reminder, calculated quote data can depend on the quote context from the CRM, but must never depend on a particular user context.

This is because the next user accessing a quote will naturally re-populate the quote context from the CRM, and so the data cannot be altered according to the last user connected, bearing in mind that several users may see the quote in competition.

The same applies to the management of user rights, which may be based on fields, but which, in this case, cannot be conditioned by data from a particular user context, as otherwise one user could take advantage of the acces rights of another user.

However, in the case of user rights, session variables offer the very possibility of conditioning user rights to a particular user context, as these variables are specific to the user session.

In conclusion, it is imperative never to store data specific to a particular user in a field, although such data can be used to manage access rights via session variables.

Some restrictions can be set to ensure a safe usage of Performance Quoting.

Those limits will be defined based on the current state of the quote, including fields values, CRM information and current user attributes (such as its profile).

Session states are used in order to define user permissions on some spreadsheet or quote objects. The system will go a through a matching mechanism based on fields or session variables to identify which session states are valid for the current quote session. This matching can be based on user related values. Several session states can be assigned to one quote session.

Restrictions can be declared on the global Quote level, on each step or page, on actions, but also on columns, fields or line types, with some distinct capabilities on each :

Quote level

  • The access can be completely disabled on a quote.
  • The access can be declared as read-only.
  • It can be disabled to delete lines from the quote.
  • It can be disabled to add lines in the quote.

Step, Page and Actions level

  • The access to some of those elements can be disabled.

Columns, Fields

  • Those elements can be individually hidden.
  • Those elements can be individually set as read-only.

Line templates

  • Line templates can be individually set as read-only
  • The capability to add some line templates can be disabled
    • In case of Folder or Specific kind of lines, the action to add those lines templates will be disabled.
    • In case of Product kind of line, the system will not authorize to add products that should match with that line template.
  • The capability to delete some line templates can be disabl

Cells

  • The capability to edit some cells can be disabled

User permissions will apply as well for API usage, and when importing data through the XLSX import functionality.