Organisation overview
The Organisation page (route /org-admin) shows the top-level settings for the organisation you are signed into and the administrator groups that control who can administer it. Every organisation in Agilicus AnyX has exactly one such overview, and it is where you manage the identity of the tenant itself: the contact email used by Agilicus, the external identifier you can attach, the subdomain your users access, and how new users are onboarded.
Purpose
An organisation (a tenant or project in other systems) is the primary span of control for permissions, users, billing, and resources. The overview screen combines two things:
- Organisation settings: the fields that identify the organisation and govern how users are created and how multi-factor authentication is enforced.
- Administration permissions: the system groups (
sys-admin,sys-apps-admin,sys-users-admin) that define who administers the whole organisation, its applications and resources, and its users.
See Organisation in the glossary and the web guide’s Organisation page.
Why use it
- Set or change the contact email that receives Agilicus correspondence.
- Attach an external identifier (for example your internal tenant ID) to the organisation.
- See the subdomain your organisation uses, which cannot be changed once set.
- Control the number of days a user has to enrol in multi-factor authentication after first sign-in.
- Choose whether users are created automatically when they authenticate for the first time.
- Disable the user-facing request-access flow for the whole organisation.
- See who is in each administration group and adjust group membership.
When to use it
- During initial setup, to confirm the organisation details and the administration groups.
- When a new administrator joins and needs access to the portal.
- When an administrator leaves and their access must be removed.
- When you are planning to delete the organisation and everything in it.
Prerequisite: you need the permissions of a user in one of the administration groups (or equivalent permission grants). The page shows a no permissions message if you cannot view or edit these settings.
How to use it
- Open Organisation > Overview from the left navigation.
- Review the organisation name at the top of the page (in this guide’s example, Dbt).
- Update Contact Email if the current contact has changed. The field is a type-ahead list of users in the organisation. Changes apply when you leave the field.
- Set External ID to your own reference for the organisation, if you use one.
- Leave Subdomain as it is: it is read-only because it is fixed once the organisation is provisioned (here
dbt.agilicus.cloud). - Set Days Until Multi-Factor Enrollment Expiry to the number of days a new user has to set up multi-factor authentication.
- Toggle Auto Create Users if you want users to be created automatically when they sign in for the first time, and Disable User Requests to turn off the request-access flow.
- Review the Permissions table and use each group’s row to manage membership (see Groups).
- To delete the organisation, use DELETE ORGANISATION and confirm in the dialog (see Deleting the organisation).
Fields and controls reference
| Field or control | Purpose | Required | Default | Valid values | Notes |
|---|---|---|---|---|---|
| Contact Email | The email address Agilicus uses to contact the organisation | Yes | The sign-up contact | A valid email address | Type-ahead list of users in the organisation; applies on blur |
| External ID | Your own identifier for the organisation | No | Empty | Free text | Useful when you map the organisation to an internal system |
| Subdomain | The DNS subdomain all users and applications use | Yes | Assigned at sign-up | Fixed | Read-only once provisioned; shown as APP. |
| Days Until Multi-Factor Enrollment Expiry | Days a new user has to enrol in multi-factor authentication | Yes | 1 | A number of days, 0 or greater | 0 means no grace period |
| Auto Create Users | Whether users are created automatically on first sign-in | No | Off | On or off | With this off, an administrator must create users first |
| Disable User Requests | Whether users can request access to resources | No | Off | On or off | Hides the request-access flow from users |
| DELETE ORGANISATION | Schedules deletion of the organisation and its data | n/a | n/a | Confirmation required | Disabled once deletion is scheduled |
Permissions table
The permissions table lists the system administration groups:
| Group | Who belongs in it |
|---|---|
| sys-admin | Users who administer all aspects of the organisation |
| sys-apps-admin | Users who administer applications and resources (typically developer or IT roles) |
| sys-users-admin | Users who administer the users of the organisation, including permissions and group membership (typically team leadership roles) |
Hover over a group name to see its description. Use the group’s row to manage who is in the group; see Groups for the full group management screen.
Dialogs and popups
Deleting the organisation
DELETE ORGANISATION opens the deleting organisation confirmation dialog. It warns that you are permanently deleting the organisation and all of its associated applications. To proceed you must:
- Enter the organisation name exactly as shown.
- Choose a Reason for Deletion from the list (customer service, ease of use, not used enough, switching service, cost, quality, missing features, or other).
- Optionally add Additional Comments.
- Select Delete to confirm, or Cancel to back out.
After confirmation the organisation is scheduled for deletion and the delete button becomes disabled, with a tooltip showing the scheduled deletion date. Deleting an organisation is irreversible and cancels the subscription. The cancellation feedback you provide is recorded.
Configuration versus diagnostics versus confirmation
- Configuration: the organisation settings (contact email, external ID, multi-factor enrollment window, auto-create users, disable user requests).
- Diagnostics: the organisation name, subdomain, and administration group membership are informational views rather than diagnostic counters.
- Confirmation: deleting the organisation is a destructive confirmation. It requires typing the organisation name and choosing a cancellation reason.
Pagination and async behaviour
- The Permissions table pages at 25 rows per page. The paginator shows the total; use the page controls to move through the administration groups when there are more than 25.
- Organisation settings changes are applied asynchronously: after you edit a field and leave it, wait a few seconds and reload the page to confirm the change. A notification confirms each update.
- Deletion is applied asynchronously: after confirming, the billing account refreshes and the button greys out with the scheduled deletion date.
Troubleshooting
- The page shows a no-permissions message: your account is not in one of the administration groups. Ask a
sys-adminto add you. - I cannot change the subdomain: it is fixed once the organisation is provisioned. Create a sub-organisation instead if you need a separate domain (see Sub-organisations).
- The delete button is disabled: the organisation is already scheduled for deletion, or you lack owner permission. Hover over the button for the reason.
- A user cannot sign in with multi-factor authentication: check the enrolment expiry window. If the grace period has passed, use the Authentication audit to see the sign-in failures and reset the user’s multi-factor token (see the web guide’s Reset multi-factor token).