Department changes: update access without carrying every old permission forward

Autom Mate Team · Practical example

When someone changes departments, use Autom Mate to coordinate new access and make old permissions an explicit decision.

Treat the move as a small service

  1. Read the approved change. Collect employee ID, old and new department, manager and effective date.
  2. Compare the access packages. Identify permissions to keep, add and review for removal. Flag individual exceptions rather than guessing.
  3. Confirm the transition. Use your existing approval process for sensitive access and any temporary overlap.
  4. Apply the changes. Run the configured directory and application steps. Update the manager or department fields where those systems require them.
  5. Check and report. Read back the result, record exceptions and tell the new manager what remains.

Example: a move from Support to Finance may require a new application role, removal from a support group and a short handover period.

Start with two department profiles and one application. Avoid copying another employee’s full access as the default package.

Completion check: the new role works, agreed removals are confirmed and any temporary overlap has an owner and end date.

Map actions and data in a Hyperflow

Where do department changes originate in your organisation? Comment with the systems and the part that is still manual; omit employee data.