ActiveManage can act as a sign-in provider for other websites and applications. Rather than your users holding a second set of credentials somewhere else, that other application sends them to you to sign in and receives confirmation of who they are.
This is the opposite of the Single Sign-On section. There, ActiveManage consumes somebody else's sign-in. Here, ActiveManage is the sign-in source.
What you can use it for
- Adding "Sign in with your account" to a companion website, mobile app or intranet tool.
- Letting your own front-end applications authenticate against the platform.
- Giving a background integration its own credentials.
- Sign-in on devices with no keyboard, such as televisions.
Where to find it
Architect Panel → Integration & Connections → OpenID Connect Provider. Users see their side of it on the Connected applications card on their own account page.
Is this what you need?
It is a substantial feature with real security consequences, so it is worth checking it is the right tool:
- To let another application sign users in as your users — yes, this is it.
- To let another system read or write data with no user involved — look at API Clients and API Server first; they are simpler.
- To let your users sign in with an account they hold elsewhere — that is Single Sign-On, not this.
Worked Examples
- Customer portal plus a mobile app: one account, one sign-in, across both.
- Partner integration: a partner's system signs your shared users in without holding their passwords.
- Internal tooling: several small internal tools all authenticating against the main platform.