Product platform

Roles and permissions, controlled in SortX.

Sales, lettings, property management, accounts and directors need different access. SortX controls what people and agents can read, draft, approve, send, sign and pay.

Live work queue

SortX

Define role

Permission model sets access by role and branch.

Set powers

Permission model controls agent capabilities separately.

Review access

Permission model protects client account and AML data.

Connected to the rest of the operating stack

  • Inbox
  • Tasks
  • Calendar
  • Contacts
  • Properties
  • Documents
  • Approvals
  • Reporting

What this changes day to day.

The workflow follows the property, contact, tenancy, repair, document or ledger item behind the work.

Access by role and branch

Sets access by role and branch.

Controls agent capabilities separately

Controls agent capabilities separately.

Client account and AML data

Protects client account and AML data.

Approval for sensitive actions

Requires approval for sensitive actions.

Permission changes

Records permission changes.

Temporary cover without shared logins

Supports temporary cover without shared logins.

Signals a manager can read quickly.

Short status markers for scanning the day without opening every record.

Role-based

access control

Agent powers

separate from users

Audit

on changes

The working view stays close to the record.

Each item shows enough context for staff to act, approve, or leave the agent to continue.

  • Access by role and branch. Sets access by role and branch.
  • Controls agent capabilities separately. Controls agent capabilities separately.
  • Client account and AML data. Protects client account and AML data.
  • Approval for sensitive actions. Requires approval for sensitive actions.

Workflow view

Branch policy applied

Live

Define role

Permission model sets access by role and branch.

role policy

Set powers

Permission model controls agent capabilities separately.

agent limits

Review access

Permission model protects client account and AML data.

access log

Audit

Permission model requires approval for sensitive actions.

permission review

How it works in the branch.

Why roles and permissions needs its own workflow

In a UK estate agency, this work crosses desks: negotiators, administrators, property managers, accounts, contractors, clients and compliance owners all need the same facts. SortX keeps the work on the operating record instead of spreading the detail across personal inboxes.

The permission model does the repeatable work first: reading, checking, drafting, matching and opening the next task. Anything that changes a client position, spends money, sends a sensitive message or affects compliance can be held for approval.

How the branch stays in control

Managers can set owners, SLA clocks, approval limits and escalation rules around this workflow. Staff can still take over manually when a case needs judgement, and the record shows what the agent did before the handover.

That matters when the risk is too much access in a busy branch. SortX gives the team the detail they need without asking them to hunt through tabs, exported reports or old message threads.

Common questions

Practical details for directors, branch managers and operations teams.




Put roles and permissions into the operating queue.

SortX gives team access and agent powers a clear owner, a live status and a controlled approval path.