Permissions

Easily control what actions users can perform in the data grid. Default permission is org-wide; custom permissions can be assigned to permission sets or profiles.

How to open

Go to the Coconut Grid Settings tab and click Permissions to open the Permissions page.

Add permission

  1. Click Add from the quick buttons to open the New Permission dialog.

  2. Enter the following fields:

    • Label – display name of the permission.

    • Name – unique API name, must start with CG_.

    • Description – optional note about the permission.

  3. Click Save.

Edit permission

  • Click the edit icon of a permission record to open the Edit Permission dialog. The input fields are the same as Add.

  • Click the permission label to open the permission detail page. From there, you can:

    • Modify the permission details.

    • Configure default object permissions.

    • Enable object-level access control to grant additional permissions per object.

Options:

  • Show Checked Only – display only enabled permissions.

  • Enable Object-Level Access Control – turn on per-object access.

  • Save – save current permission changes.

  • Return – return to the Permissions page.

Delete permission

  1. Select the permissions you want to delete.

  2. Click Delete from the quick buttons and confirm.

Default permission cannot be deleted.

Assign permission

Every custom permission excluding the default is created as a Custom Permission in Salesforce.To make it effective, you must assign it to a Permission Set or Profile.

Assign to a Permission Set:

  1. In Salesforce Setup, go to Permission Sets.

  2. Select the target Permission Set.

  3. In the Custom Permissions section, click Edit.

  4. Move your custom permission to Enabled Custom Permissions.

  5. Click Save.

Assign to a Profile:

  1. In Salesforce Setup, go to Profiles.

  2. Select the target Profile.

  3. Scroll to the Custom Permissions section and click Edit.

  4. Enable the desired custom permission.

  5. Click Save.

Behavior details

  • Default permission applies org-wide and cannot be deleted.

  • Custom permissions must be explicitly assigned to a Permission Set or Profile to take effect.

Last updated