Clients
Manage client permissions
Control which staff members can see a client and understand the separate M-Files and Abacus restrictions.
Client visibility controls access for people in your Didyma organization. Set it when creating a client or update it later from Client Info.
All members
Choose All members when every member of the organization should be able to find and open the client.
Limited access
Choose Limited when the client should only be available to selected staff members. Use Add User to add the people who need access and remove users who no longer need it.
A limited-visibility indicator helps distinguish restricted clients in the client list. The client owner keeps access, and organization administrators can access all clients.
Review the list whenever the engagement team changes. Restricting a client can affect access to its documents, integrations, and Year-End Close forms.
Contacts are not staff permissions
A primary contact or other client contact is part of the client record. Adding a contact does not grant that person access to the Didyma organization or the client workspace. Manage staff access through the client visibility settings.
M-Files restrictions are separate
M-Files has an organization-level Restricted customers setting. It can limit M-Files document access for selected customers to organization administrators. This is separate from the Didyma client’s All members or Limited visibility.
When both controls apply, review both settings. Changing one does not automatically change the other. See Connect M-Files.
Abacus restrictions are separate
Client visibility in Didyma does not control which Abacus mandants can be linked. Setting a client to Limited is not enough to protect an Abacus mandant: a user could link another Didyma client that they can access to the same mandant.
To keep a mandant available in Didyma while limiting who can link it, block the mandant in the organization’s Abacus settings. Only organization administrators can link a blocked mandant.
If the mandant does not need to be accessed through Didyma at all, restrict it in Abacus instead. Give the Abacus users used by Didyma access only to the mandants that should be available in Didyma. See Restrict access to Abacus mandants.