Entities - Permissions: Perimeters and Selective Access

Modified on Fri, 19 Jun at 11:41 AM

The Perimeters feature gives your organization granular control over who can see and edit which entities in the Legal Entity Management module. Define entity perimeters aligned with your organizational structure, assign teams accordingly, and restrict access to sensitive data categories such as shareholding, delegations, or capital management.


✅ Who Is This For?

  • Legal ops managers and system administrators responsible for configuring access rights in the platform.
  • Regional or divisional legal teams that need to work only within their own scope of entities.
  • Compliance officers managing data confidentiality and access governance across entities and jurisdictions.

⭐ When Is It Useful?

This feature is key when:

  • Your organization manages entities across multiple countries or regions, and each team should only access their own scope.
  • Certain data categories such as shareholding, delegations, or capital transactions must be restricted to specific users.
  • You need to give external collaborators read-only access to a subset of entities without exposing your full entity portfolio.
  • Compliance requirements mandate that data access be strictly controlled and auditable by perimeter.

✨ Key Benefits

  • Precise access control: define exactly who can view or edit which entities and which data categories.
  • Aligned with your org structure: perimeters map directly to your geographic, divisional, or functional organization.
  • Reduced data risk: prevents accidental or unauthorized access to sensitive entity information.
  • Multi-team collaboration: teams can work in parallel on their own perimeters without interfering with each other.
  • Compliance-ready: supports internal governance policies and data protection requirements.

✅ Step-by-Step Guide

Step 1 - Define entity perimeters

  1. Go to Settings in the Legal Entity Management module.
  2. Navigate to Permissions then Perimeters.
  3. Click Create a perimeter and give it a name (e.g. France Entities or EMEA Entities).
  4. Select the entities that belong to this perimeter and save.

Step 2 - Assign teams and users to perimeters

  1. In the perimeter settings, click Add team or user.
  2. Select the team or individual user you want to assign.
  3. Define their access level: Full access, View only, or Restricted access for specific data categories only.
  4. Save your configuration.

Step 3 - Configure selective access to data categories (optional)

  1. Select a team and click Manage data category access.
  2. Choose which categories the team can access: Overview, Instances, Shareholding, Delegations, Capital Management, etc.
  3. Save your settings.

◼ Limitations and Known Constraints

  • Users outside all defined perimeters will only have access to the Overview section of entities not in their perimeter.
  • Perimeter configuration requires administrator rights. Standard users cannot create or modify perimeters.

❓ FAQ

What happens if a user is not assigned to any perimeter?

Users who are not part of any perimeter will only see the Overview section for entities outside their scope. They will not have access to sensitive data categories.

Can the same entity belong to multiple perimeters?

Yes. An entity can be included in multiple perimeters, allowing different teams to have different levels of access to the same entity.

Can I give a team read-only access to a perimeter?

Yes. When assigning a team to a perimeter, you can choose View only access. The team can consult entity data but cannot make any changes.

Who can create and manage perimeters?

Only users with administrator rights in the Legal Entity Management module can create, edit, or delete perimeters.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article