CRMJettyBack to crmjetty.comContact us
Menu
Docs / Guides

CRMJetty Portal

Works with
Docs / Dynamics 365

Dynamics 365 Customer Portalv6.3.0

Docs / Salesforce

Salesforce Customer Portalv6.3.0

Docs / Business Central

Business Central Portal

Guides / Roles and permissions

How to Give Portal Users Account-Level Record Access

5 min readUpdated
Short answerGo to Settings → User Settings → Portal User Roles and create or edit a role. In Entity Permissions, select View for the entity, set Relationship Type to Account, Account with My Records or Account with All Records, and select Save. Then assign the role to the portal users.

By default, a portal user sees only the records linked to their own contact. If several people from the same company use the portal, you can let them see the records of their whole account, such as every case or order the company has, by changing the relationship type on their role.

Before you start

How relationship types control record access

The Relationship Type you set for each entity in a role decides which records portal users with that role can access.

Relationship type Portal users can access
Contact Only records related to their own contact profile.
Account Records tied to their associated account.
Account with My Records Their own records within the associated account.
Account with All Records All records within their associated account, including other users’ records.

Note: In Business Central, portal users are linked to customers or vendors. The relationship types available depend on your connected system.

Set account-level access on a role

  1. Go to Settings → User Settings → Portal User Roles.
  2. Select Create to add a role, or select the three dots (…) next to a role and then the Edit icon.
  3. In Entity Permissions, find the entity, for example cases or orders.
  4. Select View. You must select View before you can set the other permissions.
  5. In Relationship Type, select Account, Account with My Records or Account with All Records.
  6. Select Add, Edit or Delete if portal users should also change these records.
  7. Repeat for each entity that should use account-level access.
  8. Select Save.
Entity Permissions on the Edit Role page with View selected for Cases and the Relationship Type drop-down open on Account with All Records
Entity Permissions on the Edit Role page with View selected for Cases and the Relationship Type drop-down open on Account with All Records
Entity Permissions on the Edit Role page with View selected for Cases and the Relationship Type drop-down open on Account with All Records
Entity Permissions on the Edit Role page with View selected for Cases and the Relationship Type drop-down open on Account with All Records

You can mix relationship types in one role. For example, set Contact for an entity that holds personal data and Account with All Records for cases, so every user from a company sees the company’s cases.

Important: Add, Edit and Delete apply to every record the relationship type makes visible. If you combine Account with All Records with Edit or Delete, portal users can change records created by their colleagues.

Assign the role to portal users

The new access applies to every portal user who has the role. To give the role to more users:

Narrow account-level access with workflows

Account-level access shows every matching record in the account. To hide some of them, for example closed cases, or to remove edit or delete rights on records in a certain status, add a workflow for the role under Settings → Portal Settings → Workflow Management. See How to Restrict Record Access with Conditional Workflows.

Troubleshooting

A portal user still sees only their own records: Check that the user has the role you edited, and that the entity’s Relationship Type in that role is an account option, not Contact. Then check that the user’s contact is linked to the right account in your CRM.

A portal user sees records from the account but can’t edit them: Select Edit for the entity in the role. Also check whether a workflow removes edit rights for those records.

Did this solve it?No, contact support