How to Delegate Access to another LawPage
Explanation
Section titled “Explanation”Delegated Access allows one LawPage tenant to grant controlled access to another LawPage tenant. This enables collaboration across organisational boundaries — for example, allowing another firm or entity to manage diary entries or interact with matters without merging systems.
This feature is designed to support:
- Cross-entity working relationships
- Shared diary management
- Controlled access to matters
Access is granular and permission-based, meaning:
- A tenant can decide which other tenant is allowed access
- The receiving tenant selects which of its users will act as delegates
- The granting tenant must then activate and assign permissions for those users
The model intentionally separates:
- Tenant-level delegation (who is allowed in principle)
- User-level delegation (which individuals are proposed)
- Permission assignment (what those individuals can actually do)
This layered design supports:
- Clear accountability
- Controlled supervision
- Compliance with professional obligations
When acting as a delegate, the user operates in a distinct context, visually differentiated in the interface (e.g. menu colour changes), but retains:
- Their own dashboard and personal diary
- The ability to perform permitted actions within the delegated tenant
Getting Started
Section titled “Getting Started”To enable delegated access between tenants, both tenants must participate in the process:
Granting Tenant (Originating System)
Section titled “Granting Tenant (Originating System)”- Navigates to System Settings → Business Details → Delegated Trading Entities
- Adds the external tenant as a delegate
- Defines high-level capability (e.g. diary management)
Receiving Tenant
Section titled “Receiving Tenant”- Selects which of its users will act as delegates
- Confirms user-level participation
Granting Tenant (Finalisation)
Section titled “Granting Tenant (Finalisation)”- Activates the delegate user
- Assigns role and permissions
Once completed:
- Delegate users can switch into the external tenant
- Delegated actions can be performed within the authorised scope
How-To Guide
Section titled “How-To Guide”1. Add a Delegated Trading Entity
Section titled “1. Add a Delegated Trading Entity”- Go to System Settings
- Navigate to Business Details
- Scroll to Delegated Trading Entities
- Click the Add (green button)
- Select the external trading entity
- Choose high-level permissions (e.g. Manage Diary)
- Click Create
2. Receiving Tenant Adds Delegate Users
Section titled “2. Receiving Tenant Adds Delegate Users”Within the receiving tenant:
- Navigate to Delegated Users
- Select the inviting tenant from the list
- Click the Add (+) button
- Choose a user
- Save
3. Activate and Assign Permissions (Granting Tenant)
Section titled “3. Activate and Assign Permissions (Granting Tenant)”- Return to Business Details → Delegated Users
- Locate the newly added user
- Set status to Active
- Open user details (View → Edit)
- Assign:
- Role (e.g. Admin)
- Specific permissions (e.g. Manage Diary)
- Click Update
4. Accessing a Tenant as a Delegate
Section titled “4. Accessing a Tenant as a Delegate”- Log in as the delegate user
- Select the delegated tenant (e.g. Boanta v Rasband)
- Confirm visual indicator of delegated mode (e.g. interface colour)
Reference
Section titled “Reference”Delegated Access Model
Section titled “Delegated Access Model”| Layer | Description |
|---|---|
| Tenant Delegation | One tenant invites another to access its system |
| User Selection | Receiving tenant nominates users |
| Activation | Granting tenant activates users |
| Permissions | Granting tenant defines role and capabilities |
Key Entities
Section titled “Key Entities”| Entity | Description |
|---|---|
| Delegated Trading Entity | External tenant granted access |
| Delegate User | Individual user from external tenant |
| Granting Tenant | Tenant providing access |
| Receiving Tenant | Tenant receiving access |
Permissions and Roles
Section titled “Permissions and Roles”| Field / Setting | Description | Notes |
|---|---|---|
| Active Status | Enables or disables delegate access | Must be manually set |
| Role | Defines permission profile (e.g. Admin) | Determines scope of actions |
| Manage Diary | Allows diary interaction | Explicitly assigned |
| Other Permissions | Not shown in transcript | Needs confirmation |
Behaviour Observations
Section titled “Behaviour Observations”| Behaviour | Description |
|---|---|
| Visual Indicator | UI changes (e.g. orange menu) when acting as delegate |
| Dashboard Context | Remains user’s own dashboard |
| Diary Scope | Can access and manage diaries across entities |
| Multi-Entity Selection | Diary entries can be created under different trading entities |
Dependencies
Section titled “Dependencies”| Dependency | Requirement |
|---|---|
| Two Tenants | Both must exist and be configured |
| Mutual Configuration | Both tenants must complete their respective steps |
| User Activation | Required before access is usable |
| Role Assignment | Required to enable functional access |
Validation Points
Section titled “Validation Points”| Validation | Trigger |
|---|---|
| User Not Visible | Delegate user not yet added by receiving tenant |
| User Inactive | Activation not completed |
| Permission Failure | Role or permissions not assigned |
| Diary Visibility Issues | May require re-login (observed) |