Permissions Setup

Access boundaries that match real firm work

Permissions are not only about keeping files private. They decide how work moves through the firm, who can touch sensitive material and where approval sits before a matter shifts stage. For South African law firms handling client records, draft agreements, affidavits, discovery bundles and internal notes, those boundaries need to be plain and consistent.

We set access rules around roles, teams, matter groups and document types. That can mean one partner seeing every live file in a department while a paralegal only sees assigned matters, or an operations user handling billing and admin records without opening legal content that is not theirs to view. We also account for shared work across Johannesburg, Pretoria, Cape Town and other offices when the same matter passes between teams.

• Role based access for attorneys, paralegals and operations staff
• Matter level visibility for active, closed and archived files
• Template edit rights separated from template use rights
• Evidence access controls for review, tagging and export
• Approval steps for publishing or locking final documents

What the permissions setup covers

The setup covers the daily controls that keep document assembly and matter management orderly. We map who can create a matter, edit fields, upload evidence, change deadlines, approve templates and export bundles. Where a firm works with more than one department, we can split access so staff see only the work that belongs to them, while senior staff keep oversight across the full caseload.

We also shape the permissions around the way evidence is handled. Searchable review queues, redacted copies, source uploads and final exports often need different levels of access. That matters in firms that deal with high volumes of client material, because a clean queue is not the same as full open access. POPIA aware controls are part of the picture here, together with sensible audit trails and staff login rules.

• User roles and sub roles for different levels of responsibility
• Field editing rules for matter details, dates and status updates
• Document open, edit, approve and export permissions
• Evidence queue access, tagging rights and download limits
• Admin controls for user creation, deactivation and rights changes

How the setup work moves from map to live use

We start by mapping the firm structure as it works now, not as it looks on paper. That includes practice areas, office groups, support roles and any unusual approval paths. From there we define the access matrix, test it with sample users and check that day to day actions still feel natural for the people who use the system most often.

After the rules are agreed, we configure the environment and run checks against real work types such as matter opening, template drafting, evidence review and document export. If a firm needs separate setups for Sandton and a second office, or different access for litigation and conveyancing teams, those layers are set before wider use begins. The final step is staff verification, where each role is checked against the tasks they actually perform.

• Role mapping and access matrix planning
• Configuration of matter, document and evidence rights
• Sample testing with real firm scenarios
• Correction of gaps, overlaps and extra access
• Go live sign off after role checks are complete

Turnaround that follows the shape of the firm

Turnaround depends on how many roles, offices and work types need to be covered. A small practice with a few clear user groups usually moves faster than a multi office team with separate approval chains, custom templates and evidence controls. The main variable is not software effort alone, but the number of decisions the firm needs to settle before access can be locked down.

Where permissions sit alongside template builds, workflow configuration or data migration, we usually sequence the access work early so later setup does not need to be redone. If a firm already has a working structure and only needs rights refined, that is usually a neater exercise than rebuilding access from scratch. The process is planned around practical deadlines in legal work, so there is less risk of users being blocked when matters are live.

Pricing approach for permissions work

Pricing is based on the depth of configuration rather than a flat one size fits all pattern. A straightforward role structure with a limited number of user groups will cost less than a setup with multiple offices, layered permissions, evidence controls and custom approval routes. If the firm wants permissions tied into secure hosting, incident controls or a wider onboarding project, the scope is priced as part of the full implementation plan.

We usually quote after the firm has shared its role list, office structure and the main actions each user group must be able to perform. That makes the scope clearer and avoids vague pricing based on guesswork. It also helps when a firm wants only one part of the access structure handled first, then the rest phased in after internal review.

• Pricing reflects number of users, roles and matter groups
• Custom approval logic adds scope
• Evidence and export controls may add setup time
• Multi office firms need more mapping and testing
• Security requirements can shape the final quote

Aftercare once permissions are live

Once permissions are active, firms often need the structure checked after staff changes, new practice groups or revised approval paths. Aftercare covers those adjustments, plus help with rights for new users, removed users and temporary access changes during leave or secondment. It also covers reviews where a firm notices that a person has too much visibility or cannot reach work they need for daily tasks.

We also look at the admin side of access, including who may create users, change roles and review logs. That helps keep the system tidy as the firm grows, and it reduces the risk of old rights lingering in place after staffing shifts. Where needed, we also align permissions with broader security settings so the controls stay sensible for a legal environment handling confidential material.

• User access reviews after staffing or role changes
• Adjustments to approval rights and admin rights
• Support for new departments or office groups
• Checks on access to sensitive matter records
• Alignment with security and audit settings

What the final permission set needs to show

A good permissions setup should be easy to explain to the firm and strict enough to protect matters, templates and evidence. Attorneys should see the files they manage, paralegals should work inside their assigned boundaries, and operations staff should carry out admin tasks without opening areas they do not need. The structure should also allow senior people to review activity without creating confusion for everyone else.

For South African firms, that balance matters in day to day legal work where deadlines shift, teams overlap and information moves quickly between offices. A clean access structure keeps the system usable without making it loose, and it gives the firm a clearer footing for secure document handling over time.