Roles and access permissions in a client dashboard

Roles and access rights in the client’s account determine who sees projects, uploads documents, confirms changes, and manages participants. If we limit ourselves to the names “client” and “administrator”, important differences will remain undescribed. For example, an accountant may need invoices, but a project employee may only need tasks and materials in his area.

You should start with work activities and data boundaries, rather than with a list of screens. These rules are then turned into an access matrix and checked in the front-end and back-end. Below is a practical procedure for preparing requirements for a new dashboard or modifying an existing one. It helps to agree on powers before controversial situations arise with documents and responsibilities.

1. Describe the users and their tasks

Make a list of people who will actually use the dashboard: customer representative, project employee, accountant, manager and administrator. These are examples and not a required set of roles. For each participant, write down the tasks and data without which he will not be able to complete them. Do not give access to an entire section just because one of its functions is needed by a specific person.

Specifically check whether one person can work with several organizations or projects. In this case, the role is not enough: it is important within which organization the user currently operates. It is convenient to add the answers to the list of functions of the first version of your client dashboard. This will allow each permission to be associated with an understandable work task, rather than a developer guess.

2. Create an action and permission matrix

In the rows of the matrix, list the actions: open the project, download the document, upload the file, change the status, confirm the estimate, invite the employee and withdraw the invitation. Specify the roles in the columns. For each intersection, write down permission and conditions: for example, only your own project, only organizational documents, or only assigned tasks. A general “access to documents” checkbox is often not enough.

Separate viewing, creating, editing and deleting. The right to download an invoice does not mean the right to replace it with a file, and downloading material does not have to provide the opportunity to delete the manager’s document. For confirmations and financial actions, determine who can perform them on behalf of the organization. The matrix should be short enough for discussion with the process owner and precise enough to verify the result.

3. Enforce permissions on the server

The hidden button helps explain the interface, but does not protect the data on its own. The server must check the right to a specific action and a specific object. Logging into your account confirms the user’s identity, but does not yet give him the right to open any project. The rule must apply to both the page and the individual file download or status change request.

The OWASP Authorization Guide lays out the basic principles of minimum required authority, default denial, and checking permissions on every request. For the account, this means that the new section does not become public due to a missing condition. When changing rules, you need to check all associated paths, including search, export and attachments, and not just the main project card.

4. Separate ownership from roles

Two users with the “client” role can have completely different projects. Therefore, the verification must take into account the user’s relationship with the organization and the object. Separately define the behavior of shared projects, invited participants, and archived materials. The conditions must be the same for the list, card, search and download: you cannot hide the project in the list, but leave the document accessible via a direct link.

The file requires the same access rule as an entry in the account. If the document is stored at a public address, checking when opening the page will not solve the problem of its further distribution. The method of storing and issuing documents must be chosen based on the purpose of the materials. In the requirements, indicate which files are intended for public viewing and which are released only after checking the user’s current access.

5. Plan invitations and access revocation

The invitation must connect the person to the desired organization or project and a predefined role. Write down who can send it, whether the invitation can be canceled, and what happens after the invitation expires. Do not make registration by invitation an automatic basis for granting extended rights. After accepting the invitation, the user must understand which workspace he is in.

Firing an employee or ending participation in a project requires a separate scenario. Determine how access is revoked, what happens to active sessions and temporary links. Already downloaded files technically cannot be returned by simply deleting the role. The history of actions should preserve a clear performer; You should not replace old entries with the name of the new employee to whom the tasks were transferred.

6. Separate administration from daily work

The normal work of a manager and setting up access rules are different powers. If a person only processes enquiries, they do not need to be given the ability to appoint administrators. For membership changes, bulk exports, and other sensitive activities, define separate permissions. It is difficult to identify the performer for a shared account, so individual accounts with a clear purpose are preferable.

Record significant changes: who performed the action, what object was affected, what changed and when. Do not turn the journal into a copy of all documents or correspondence. Access to the journal itself also needs to be determined. For urgent exceptions, indicate the reason, the person approving, and the term of office. Otherwise, a temporary solution may quietly become permanent access, which no one will review.

7. Test allowed and denied actions

Prepare test accounts of different roles and two independent clients. Check not only for success, but also for failure: someone else’s project, someone else’s attachment, unavailable exports, and action after role revocation. Following the saved link should not bypass the changed restrictions. These tests are performed in a consistent test environment with synthetic data, rather than on real customer documents.

Test role combinations and cross-organization transitions, if applicable. After removing access, return to the already open tab and try again. Separately, make sure that the cache does not give the answer from one user to another. Record the expected outcome of each scenario and repeat associated checks after rights updates, searches, document loading, or API loading. One successful administrator login is not enough to accept the account.

What to include in dashboard requirements

To get started, prepare a list of participants, an action matrix, data ownership rules, the procedure for inviting and revoking access, as well as examples of allowed and prohibited scenarios. For each rule, assign a person to validate it from the business side. If the situation is not described, it is safer to agree on it separately than to silently expand rights to all users.

It is convenient to formalize general requirements for documents and stages using practical checklist of technical specifications, and include checks after changes in site support plan. Describe the dashboard members and the actions they need in the brief – this will help agree on the access structure before development begins.