What it is

Four separate checks decide what a person sees in DuctArchitect. Each check is set in a different place. When something is missing for a person, find out which check is stopping it.

  1. Plan. If the company's plan is pending, expired or suspended, most actions are held back for everyone. See How your company's plan status changes.
  2. Modules. On Modules & Firm Type, an Owner or Admin switches modules on or off for the whole company. A module that is off leaves the sidebar for everyone.
  3. Permissions. Each person holds permissions such as Project Management or User Management. A permission decides which menus and pages the person can open.
  4. What the person can do and see inside a module. For each kind of record (enquiries, quotations, purchase orders and so on), a role or a person can be allowed or refused View, Add, Edit, Delete and Approve. Prices, costs, profit, salary and customer contact details can be hidden, and a person can be limited to their own records or stopped from exporting lists.

Owner, Admin and Super Admin pass checks 3 and 4 completely. Checks 1 and 2 still apply to them.

How it moves

DuctArchitect works out a person's permissions in this order and stops at the first one that applies:

  1. The person's role is Owner, Admin or Super Admin: they hold every permission.
  2. The person has their own list of permissions: that list is used.
  3. Their role has default permissions set on Roles / Departments: those are used.
  4. Otherwise the built-in defaults for the role are used. For example, Manager starts with Dashboard, Project, Enquiry, Operation, Worker Tracking and Inventory Management.

When you pick a role on Add New User, DuctArchitect copies the role's defaults into the new person's own list. So a later change to the role does not reach people who already have a list of their own. See My change to a role did not reach existing users.

What a person can do inside a module and what they can see follow the same order: their own setting, else their role's, else nothing restricted.

Who is involved

RoleWhat they do
Owner, AdminSwitch modules on or off, add users and choose their permissions, edit roles.
HROpens Roles / Departments and HRMS › Employees, where roles, what a person can do inside a module and sensitive information are set. HR holds the right to manage permissions for others by default.
A person with Can manage permissions for other peopleChanges other people's permissions, but never their own, never an administrator's, and only up to what they hold themselves.