The Users page and the rights table
Super > Users opens the page ABMS - Users, where you add, edit and deactivate users, and set their access rights. It has two tabs, Users and Access groups; this page covers the Users tab. You need the Admin level on the Super area row of your rights; this is what shows the Super menu. Your user administrator sets this.
Buttons at the top
Section titled “Buttons at the top”| Button | What it does |
|---|---|
| Add user | Opens the User profile form for a new user; see Add a user. |
| Create multiple users | Opens the page for adding many users at once; see Add multiple users at once. |
| Export | Exports the user list. |
The selected user
Section titled “The selected user”| Control | What it does |
|---|---|
| User picker | Picks the user to work on; it shows names and e-mail addresses. Deactivated users are marked “Deactivated”. |
| Edit | Opens the user’s User profile form. Disabled when the picked user is deactivated. |
| Deactivate user | Deactivates the user; see Deactivate or reactivate a user. Disabled when you have picked yourself. |
| Reactivate user | Shown instead of Deactivate user when the picked user is deactivated. Reactivates the user; see Deactivate or reactivate a user. |
| E-mail and Id | The user’s e-mail address (username) and ID. |
Group membership
Section titled “Group membership”A table of every access group in your company, with a checkbox per group, the group’s name and its description. Tick or untick to add the user to a group or remove them. Removing is refused when the user is a workflow or competency responsible through that group. See Create and manage an access group.
The rights table
Section titled “The rights table”| Column | What it shows |
|---|---|
| Module name | One row per document module, one per special module (for example competency, risk management, data sheets) and one per KPI scorecard (“Kpi: <scorecard name>”, the copy for the highest year). There are also area rows that control a whole function, for example KPI, the Super area row and the reports row. |
| Access rights | The user’s own level, chosen in a dropdown: blank, Read, Edit, Create, Approve, Manage, Archive, Admin. Whether this column shows a dropdown depends on a setting that Antenor manages; if you cannot change the levels here, contact Antenor support. |
| Group rights | The highest level the user gets through access groups. Hover over it to see which group or groups give it. |
The user always has the higher of Access rights and Group rights. Choosing the blank level removes only the user’s own right; group rights still apply. Rows of a deactivated user are locked.
The levels
Section titled “The levels”| Level | What it unlocks |
|---|---|
| Read | Open and read in the module or area. For a KPI scorecard: open it, see graphs, export it. |
| Edit | Work on items you own, for example the document step you hold, or values in a KPI scorecard. |
| Create | Create new items, for example documents or KPI scorecards; on a scorecard also delete it. |
| Approve | Approve and publish documents, and be offered as a receiver on approval steps. |
| Manage | On the KPI row: adding headers and rows in KPI scorecards. On the Super area row, Manage does not give the Super menu (see below). |
| Archive | Archive and unarchive documents. |
| Admin | Everything the other levels give. On the Super area row: access to the Super menu. |
As a general rule the levels form one ladder: each level includes all the lower levels (Read is the lowest, Admin the highest). Some features need one exact level instead, so a higher level on the same row does not give them:
- The Super menu needs exactly the Admin level on the Super area row; Manage or Archive on that row does not give it.
- In a document module, adding a new value from a search-as-you-type dropdown needs exactly the Manage right on that module’s row; see The field types in a document form.
- In a document module, a person-list field can be set up to list only the users with exactly one chosen level on that module’s row.
- In Competency, View Report can be given only to users with exactly the Read right on the Competency row; see Give managers access to people in Competency.
What a level unlocks in detail is described in the articles for each module.
Which row gives what
Section titled “Which row gives what”- The Super menu (users, access groups, ownership transfer, company menus, system settings): the Admin level on the Super area row; Manage or Archive is not enough. The Super area row is not in the access group table, so it is set in the user’s own rights.
- Reports: seeing Reports in the left menu and exporting reports needs the Read right on the reports row; a report is listed in Reports and opens only when you also have the Read right on every module the report covers. Creating a report needs the Create right on the reports row. The Settings tab of a report is shown only to the report’s creator and to users with the Admin level on the Super area row, and only for a report on one module. Deleting a report needs the Create right or higher on the Super area row. See Reports: who can do what, and the Reports list, Find and read a standard report and Create a report.
- Company menus: changing a company menu also needs at least the Edit level on the company menus row, and duplicating or deleting one needs at least the Create level on that row. See Build or edit a company menu and Access rights by row and level.
- KPI scorecards: the KPI row for creating and building scorecards, and the “Kpi: <scorecard name>” rows for each scorecard.
- Actions: the Read right on the Action Manager row opens the Action Manager and lets the user add actions to a document with the flag (Create new action). New action in the Action Manager, and copying actions and creating plans there, need the Create level or higher on that row. By default every user has the Admin level on that row through the predefined Action Manager access group; a user removed from that group keeps a right on the row only if their own rights give it. See Create an action and send it to someone.
- The main area row: every new user gets the Read right on this row when their account is created. It is separate from the rights on each module; some features need it as well as access to the item, for example subscribing to a document. You cannot change your own right on this row. See Follow a document.
Superuser. When a message tells you to “contact a superuser”, contact your user administrator: the person who manages users and rights in your company.
Refusals you may see
Section titled “Refusals you may see”- “You cannot change your access rights on this area”: you cannot change your own rights on the Super area row or the main area row.
- Lowering a module right below Approve, or removing it, is refused while the user is in an active workflow or has documents in progress in that module, unless a group still gives Approve. The message names the workflow and module.
- A change that would leave part of the organization without a competency responsible is refused, with the users listed.
Next step
Section titled “Next step”Related
Section titled “Related”- The Access groups tab
- Add multiple users at once
- Deactivate or reactivate a user
- Create a report
- Build or edit a company menu
- Access rights by row and level
- User accounts: details, e-mail changes, deactivation and login
- The User profile page
- Links from ABMS: categories and what you can link to
- Messages ABMS shows, and what to do
- Words used in ABMS
- Reports: who can do what, and the Reports list
- Changing an action in detail: fields, checklist, attachments, copies and deleting