↑
← All articles

Technology decisions

Make platform administration survive an absence.

Design routine platform administration so essential changes and recovery do not depend on one available person.

A hypothetical business relies on one experienced colleague to add users, change workflow rules and speak to the platform supplier. The arrangement feels efficient until that person is away when an urgent access change is needed. Other managers know the outcome they want, but not the authorised route or the effect of making the change. Continuity is not achieved by sharing one administrator's credentials. It comes from defined responsibilities, appropriately separated access, usable records and a recovery route that another authorised person can follow.

List the administration that matters

Start with tasks that keep the service usable: adding or removing access, changing approval rules, updating reference data, reviewing failed integrations and raising consequential supplier requests. Record the frequency, business impact and information needed for each task.

Separate routine administration from changes that need broader approval or specialist support. A deputy does not need unlimited access to provide useful cover, but the business should know which gap remains and what happens when it matters.

Create an authorised second route

Give cover through named individual access with the permissions appropriate to the work, rather than a shared account. Confirm how that access is approved, reviewed and removed. Where duties should remain separate, document who requests, approves and performs the change.

Include account recovery and supplier escalation. Check which identity, contract details or authorised contacts the supplier requires, and keep that information somewhere the business can reach without depending on the absent administrator.

  • Which administration tasks are time-critical?
  • Who is authorised to provide cover?
  • Which changes require separate approval?
  • How does the supplier recognise an authorised request?

Record decisions, not only clicks

Instructions should explain the reason and expected effect of a change, not merely which menu to open. Include the checks to make beforehand, the evidence of completion and the route for reversing or escalating an unexpected result.

Keep a concise record of significant configuration changes. This helps the covering person understand the current position and reduces the risk of treating an intentional rule as an error.

Test cover during normal conditions

Use a safe representative task while the primary administrator is available. Ask the covering person to find the instructions, use their own approved access, complete the task and confirm the result. Observe where they need undocumented context or unavailable permissions.

Review the arrangement when the platform, supplier contacts or internal responsibilities change. The aim is not to make every person interchangeable. It is to prevent an ordinary absence from becoming an avoidable operational blockage.

Rethink's technology second opinions can include the ownership and operating conditions around a platform, not just its feature list.

Explore a technology second opinion →

Work with Rethink

Discuss your
project.

Talk to Rethink