Skip to main content

What roles are there in AIMZ, and what can each role do?

An overview of the roles Owner, Admin, Writer and Reader, the access levels, and what each role can do.

AIMZ has four roles you can give users:

Access control. 1: Role. 2: a user with the Reader role. 3: a user with the Admin role.

  • Owner — full access. Can give other users Admin and Owner access.

  • Admin — can administer the project and give others access (add users).

  • Writer — can register and edit all data, including the estimate and production codes, but cannot give access to others.

  • Reader — read-only access.

Access levels

Access can be given at four levels: project, department, organisation and group.

Recommended setup

A common recommendation is to give project managers the Admin role, since the Writer role cannot manage who else has access to the project.

If you need to perform an action that your role does not give access to, a user with a higher role must make the change or give you extended access. Admin and Owner can add users, but only Owner can give Admin or Owner access.

Creating and deleting projects

The highest role in AIMZ is the Owner role at organisation level (global admin).

Creating a new project requires this role. If project creation seems to hang or load endlessly without an error message, the most common cause is that the user does not have this role.

Deleting a project also requires the Owner role at organisation level (global admin). This is a deliberate restriction to prevent projects from being deleted by mistake by users with the Admin role.

Did this answer your question?