Delegated Access for Maintenance Applications
Councils need to manage access for contractors and service partners across maintenance applications. UNIFYElevate provides governed delegation of user, role and application administration. This use case focuses on who can access those systems and who can administer that access; work orders, scheduling and resource allocation remain responsibilities of the connected maintenance applications.
Who Is Involved?
- Council service owners define the applications, roles and administrative actions that can be delegated.
- Approved contractor and partner administrators manage users and access within the scope assigned to them.
- Maintenance teams use the access granted to them in the council’s connected applications.
A contractor administrator’s authority to manage access does not itself grant authority to approve work orders, allocate budgets or administer other council systems.
An Access Administration Scenario
A council works with several maintenance providers. Each provider needs to administer access for its own staff while the council retains control of application permissions.
The service owner defines the permitted roles and assigns an administrative scope to approved provider administrators. Those administrators can then manage users and access within that scope. When staff responsibilities change or an engagement ends, access changes and removal follow the service owner’s configured rules and permitted workflows.
This separates routine access administration from the council’s operational maintenance processes. The maintenance applications continue to own scheduling, task allocation, property records and work-order completion.
Define the Boundaries Before Delegating
An implementation should establish:
- Which applications and roles each provider may administer.
- Which user and access changes administrators may perform.
- Who approves changes to the scope of delegation.
- How access changes and removal are handled when staff or contracts change.
- What administrative activity needs to be retained for support and review.
UNIFYElevate’s delegated administration model keeps role scope, permissions and application boundaries under the service owner’s control. The connected applications remain responsible for their business functions and data controls. Integration requirements and available workflows should be agreed for the council’s environment rather than assumed from this example.
Explore UNIFYElevate
See how UNIFYElevate works for its delegated administration model, or return to UNIFYElevate for the product overview.
Discuss Your Maintenance Access Requirements
Tell UNIFY which council applications, contractors and service partners need delegated administration. We can discuss the access boundaries and integration requirements for your environment.