Administration, users and permissions
What you will learn
Grant company and function access using least privilege.
Worked example
Create a planning-read role, assign it to a test user and company and verify they cannot edit or open unauthorised areas.
From data to result
- 1Company
- 2Role
- 3User
- 4Access test
Customer administration manages access within the authorised configuration. It is not the APL panel and does not grant access to other customers.
- 1Open Administration with an authorised account. Define roles by area and access level: read for queries and write for supported changes.
- 2Create users with the correct type, companies, roles and status. A web-service user is for the API, not an interactive app session.
- 3Use least privilege and test authorised access, including direct URLs. Hiding a menu is not server authorisation.
- 4Credential changes may revoke sessions. Never put passwords or keys in support tickets; follow your organisation’s secure process.
Visual walkthrough
Download video- 0:00 · Open Roles in Administration.
- 0:06 · Select Consulta de producción.
- 0:12 · Review module read permissions. No permissions are saved or assigned.
Before you finish
Review users, assigned companies, roles, sessions and audit. Test with that identity, not only the administrator.
Common questions
An option is missing or I cannot edit
Check active company, licence, permissions and integration-managed fields. Do not use a direct URL to bypass restrictions.
I cannot find records
Clear filters and check page, dates and company. There may be no accessible data; do not create duplicates to test.
I saved but cannot see the expected effect
Reopen the record and verify. Saving data does not publish a required simulation. Check whether the first write succeeded before repeating it.
