How to define team permissions in a business management system

Permissions determine who can view, change, approve and export information. They should follow each person’s work and the data they may act on. This guide helps turn generic job titles into a verifiable matrix, with rules for joining, role changes and leaving the team.

By Lyntev. Updated on .
About 4 minutes to read.

The answer starts with the sourceApproved information, defined access and a verifiable answer.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Create a permissions matrix
  • Test permitted and rejected operations
  • Prepare team changes and departures

Start with actions and the dataset

A role called “team member” does not explain whether someone can view all customers, edit only their requests or export a complete list. Separate action and scope: view assigned requests, change their own schedule, approve stock adjustments or manage users. Also consider particularly restricted fields.

OWASP recommends least privilege, denial by default and checking authorisation on every application request. For business design, this means access arises from a defined need and must be demonstrable. A new feature must not remain open merely because no specific rule has yet been assigned.

Build a small, specific matrix

Choose roles corresponding to stable responsibilities rather than arbitrary individual permissions for each person. A small business may start with reception, technician and coordination. Define who approves each role and which tasks require temporary permission. If someone combines roles, make that combination visible.

The following example is fictional and applies to support requests. Role names do not represent a universal configuration. “Own” means requests actually assigned; “all” means only the authorised organisation’s scope. In a system with several companies, none of these roles should cross that boundary without an explicit, justified rule.

Build a small, specific matrix
ActionReceptionTechnicianCoordination
Create a requestYesNoYes
View requestsWithin the organisationAssignedWithin the organisation
Record an interventionNoOn assigned requestsYes
Transfer ownershipNoNoYes
Export the complete listNoNoSpecifically approved access
Manage usersNoNoSeparate administrative role

Add conditions that a job title does not explain

Some permissions depend on record status, customer relationship or approval. A technician may edit an intervention while open but need to request a correction after validation. The person responsible may approve a change within their scope without access to all system administration.

Write these conditions as verifiable rules. When assignment changes, state whether previous access disappears and what history remains viewable. For higher-consequence operations, define whether two separate interventions are required. Separating preparation and approval only works if the application prevents the same person bypassing the rule through another option.

Enforce the rule beyond buttons

Hiding a button improves the interface but does not itself control data access. The application must check the operation on the server and through alternative routes: search, export, attachments and integrations. Ask the technical team to demonstrate the rule with test accounts for different roles.

Keep personal accounts for people and separate identities for integrations. A shared administrative account makes it difficult to identify who acted or remove just one person’s access. Separate administration from daily use, protect access recovery and document who can help when the usual administrator is unavailable. The emergency account must be controlled and its use recorded.

Prepare joining, role changes and leaving

On joining, confirm identity, approved role and scope. On a role change, compare required access with existing access: adding permissions without removing old ones accumulates privileges over time. Temporary assignments need an end date or condition and someone to confirm removal.

When someone leaves, address their account, active sessions, devices and integration credentials under their responsibility. Microsoft explains that revoking access involves tokens and sessions and may not take immediate effect in every service. The procedure must therefore confirm the outcome in relevant applications, rather than merely mark a user inactive in one dashboard.

Authorisation lifecycle
  1. Request

    State the task, scope and duration.

  2. Approve

    The responsible person confirms the need.

  3. Assign

    Apply the role and conditions.

  4. Review

    Confirm use and remove what has ended.

Also test what must be rejected

Prepare fictional accounts for two roles and, where applicable, two organisations. Check one permitted and one prohibited operation for every important rule. Include attempts to open an out-of-scope record, obtain an attachment, export data and continue a session after access removal.

Record the result and context needed for investigation without copying sensitive content into technical logs. A refusal should be understandable without revealing data the person cannot access. Review the matrix for new functions, team changes, integrations or important process changes.

Also test what must be rejected
TestExpected result
Technician opens another technician’s requestApply exactly the defined scope rule.
User changes an attachment identifierNo access to unauthorised information.
Role without export permission attempts exportOperation also rejected on the server.
Person changes teamOld access reviewed, not merely new access added.
Deactivated account with an open sessionBehaviour confirmed in every application.

Keep a record enabling access review and removal

The matrix should be linked to processes and acceptance tests. Name an owner for rule approval and another for implementation where team size warrants it. A useful review can explain why every access exists and how its removal is confirmed.

Worksheet for your project

Permissions worksheet
Roles and tasks they represent:
Actions: view / create / change / approve / export / administer
Data scope for each action:
Conditions by status, assignment or organisation:
Operations requiring separate approval:
Who approves and applies access:
Joining and role-change procedure:
Temporary permissions and ending condition:
Leaving: accounts, sessions, devices and integrations:
Test accounts and prohibited operations exercised:
Necessary audit records and retention:
Review date and changes made:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.