Feature

User lifecycle management

Automate access from onboarding through role changes and offboarding.

  • Invite-based onboarding
  • Access follows role and department
  • Central offboarding from published apps
  • Every change has an audit trail

What it does

Start with the organisation model

Users sit inside departments, groups and roles, so access is inherited from how the business is structured rather than copied from a spreadsheet.

Invite people into the right place

New users join through an invitation flow, and administrators can revoke invitations that should no longer be used.

Movers change access naturally

When someone moves team, changing their role, group or department moves their access with them, instead of it being re-created application by application.

Leavers are handled centrally

Deactivate the person, or take them out of the groups and roles that grant their access, and the applications published through Besecure stop appearing for them. One action, in one place, recorded.

Setting it up

What the rollout looks like

Sync or add users

Bring users from the directory you already run, or add people directly.

Create roles and groups

Model departments, groups and role types once.

Attach applications

Assign applications to the groups and roles that need them.

Review changes

Use audit logs and reports to prove what changed and when.

Questions about user lifecycle management

Is this the same as SCIM provisioning?

No. Besecure manages the lifecycle inside its own model of users, departments, groups and roles. It does not implement the SCIM provisioning standard.

Can access be assigned without touching each user?

Yes. Access can be attached to roles, groups and departments so people inherit what their position needs.

One sign-in for every app your team uses.

Set up your organisation, connect your directory and give your people a single secure launchpad.