home

Advantage Platform Administration

Adobe Sign ServicesAiMeAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAiMeAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release

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.

Show Contents

Show Page Sections

Advantage Platform Administration

Permission Groups

Creating a Permission Group

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click Add New.
  5. Enter values in the following fields:

    Field

    Description

    Display Value

    Enter the display value (name) that is displayed as a name in the list view.

    Value

    Enter the unique value (name) for the permission group. You can enter up to 80 characters in this field.

    Description

    Enter a description of the permission group.

  6. Click Save.

You can see the newly created permission group in the list view.

Note:

The application automatically adds the View All permission to the AppRegistry object, allowing non-administrative users to view the Conga Advantage Platform administration apps. You can change the object permission if necessary.

Assigning Object Permissions

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click the permission group name link from the list page, or click the More () icon adjacent to the record and click Edit.
  5. On the Object Permissions tab, click the Add Object Permissions button.
    Note:

    The system automatically generates the "customcode" and "Configuration" object permissions when creating a permission group.

  6. Assign the required permission for the object(s).
    • Modify All: Grant all standard CRUD (Create, Read, Update, Delete) permissions.
    • View All: Grant Read permission by default.
    • Read, Create, Update, and Delete: Manage individual permissions for standard CRUD operations.
    • Read Criteria: Click the Set link in the Read Criteria column to set access criteria for specific objects. Use only queryable fields from the object to set the criteria.
    • Custom Action Permissions: Control which custom actions (e.g., activate, generate) users can perform. Click the Set link in the Action Permissions column to assign custom actions to specific objects.
    This table summarizes user permissions based on specific conditions and actions, showing what users are allowed to do in each scenario:
    ConditionActionUser Permission

    ViewAll = false,

    ModifyAll = false,

    Create = true

    Create

    The user can create a record.

    ViewAll = false,

    ModifyAll = false,

    Update = true

    Update

    		 The user can update records only if they own the record, or have edit access to a shared record.
    Note:

    The system throws a validation error if the user updates a record accessible through permissions other than owner scope (global/user/account).

    ViewAll = false,

    ModifyAll = false,

    Delete= true

    Delete

    The user can only delete records they own.

    Note:

    The system throws a validation error if the user deletes a record accessible through permissions other than owner scope (global/user/account).

    ViewAll = false,

    ModifyAll = false,

    Read= true

    Read

    The user can view a record if any scope (global, user, or account) grants access, if they own the record, or if it is shared with them.

  7. Click Save Object Permissions.

To delete an object permission, select it from the list and click the Delete Object Permissions button.

Assigning Field Permissions

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click the permission group name link from the list page, or click the More () icon adjacent to the record and click Edit.
  5. On the Object Permissions tab, find the object to modify and click the Set link in the Field Permissions column.
    This raises the ActivityHistory Fields pop-up.
  6. Apply Edit or Read Only to or deselect the fields you are modifying. All fields in an object have full read and edit access by default. This table outlines the access levels and corresponding permissions for grid and detail views.

    Access Level

    Grid View

    Detail View

    Edit

    Displays an edit icon next to the field value, allowing inline editing directly from the grid.

    Shows an edit icon next to the field value, allowing edits.

    Read-Only

    Displays a lock icon next to the field. A validation message appears on hover when edit is attempted.

    The field is disabled. A message appears on hover when interaction is attempted.

    None (no read or edit access)

    The field is not displayed in the grid.

    The field is not displayed in the record detail view.

    Note:

    You cannot change access control for system-generated fields (Created By, Created Date, Modified By, and Modified Date).

  7. Click Save.

Assigning Record-Type Permissions

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click the permission group name link from the list page, or click the More () icon adjacent to the record and click Edit.
  5. On the Object Permissions tab, find the object you will modify and click the Set link in the Record Type column.
    Selecting a record-type object (Agreement, e.g.) raises a Set Record Type pop-up. Clicking objects that lack a record type results in an error.
  6. Assign access to the record field.
    By default, all record types are accessible to all users.
  7. Click Save.

Adding Scope Permissions

Global, user, and account scopes only apply to an object if ViewAll or ModifyAll is not set up. Only queryable fields are used to set read criteria for all global and user scopes.

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click the permission group name link from the list page, or click the More () icon adjacent to the record and click Edit.
  5. Open the Global Scope, User Scope, Account Scope, Contact Scope, or Property Scope tab.
    Note: For more information on how to add property and contact scope, see Adding Property Scope Permissions and Adding Contact Scope.
  6. Set the criteria and click Apply.

Adding Contact Scope

  • You are an administrator.
  • Supplier or Account is available as the Primary Contact Object.
  • The required lookup fields exist between the Primary Contact Object and Dependent Objects.
  • The Permission Group is an External type Permission Group.
  • The external user has a contact relationship with the Supplier or Account contact object.
Important: You cannot modify the external user permissions that are provided out of the box. However, you can add permissions for custom objects and custom fields.
You can control record-level access for external users based on their relationship with a primary business object.
  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission group for external users from the list page.
  4. Go to the Contact Scope tab.
  5. Enable the required Primary Object for which you want to set the contact scope.
  6. For each Dependent Object, click set or Modify action and select the lookup field that references the Primary Object.
  7. Click Apply.
  8. Add the Permission Group to the role for the external users if it is not already assigned.
  9. Assign the updated role to the external users who require contact-based access.

Contact Scope is configured for the external type permission group. When an external user with the Permission Group accesses records, the platform evaluates the user's contact relationship and returns only records within the user's scope. The same scope applies to the configured Dependent Objects.

If the user attempts to access a record outside their scope, the platform denies access.

Verify the Contact Scope configuration with an external test user. Confirm that the user is assigned to a role containing the external type permission group and can access the expected Primary Object and Dependent Object records. Also confirm that the user cannot access records outside their scope.

Adding Property Scope Permissions

  • You have administrator access to manage roles and permission groups.
  • The required Property Objects already exist and are active.
  • The business objects you want to control include lookup fields that reference the Property Object.
  • The Permission Group is created or identified for update.

Property Scope permissions allow you to control record-level access using Property-Based Access Control (PBAC). With PBAC, you grant or restrict access based on business properties, such as classification, region, or contract group, rather than creating multiple roles.

You configure Property Scope permissions inside a Permission Group. Once assigned to a role, these permissions determine which records users can create, view, update, or delete based on the property values linked to those records.

For more information, see Property-Based Access Control (PBAC).

  1. Log in to the Conga Advantage Platform as an administrator.
  2. Click the App Launcher () icon in the top left corner, then Admin Console > Users.
  3. Click the Permission Groups tab.
  4. Click the permission group name link from the list page, or click the More () icon adjacent to the record and click Edit.
  5. Select the Property Scope tab.
  6. Search for and select the required Property Object.
  7. Enable the applicable access level:
    • First-Level PBAC Object to control objects that directly reference the property.
    • Second-Level PBAC Object to control objects that reference a 1st-level PBAC object.
    Note: For more information on first and second level PBAC objects, click here.
  8. Go to the Access Settings tab.
  9. For each available property value, assign the required CRUD permissions:
    • Read
    • Create
    • Update
    • Delete
  10. Click Save.
  11. Add the Permission Group to a role, if it is not already assigned.
Users assigned to roles that include this Permission Group can access records only when the property values match the permissions you configured. The system evaluates property-based rules automatically and filters records before users interact with them.
  • Assign the updated role to users who need property-based access.
  • Review existing Permission Groups to reduce role complexity using PBAC.
  • Test access with sample users to confirm that property values are enforced correctly.
Administrator Guide
Conga Advantage Platform Administration

October 15, 2026

Related Articles: