How Regscribe works with your organization's Entra ID
If you're the IT admin for a company whose employees will sign in to Regscribe with their work Microsoft account, this explains exactly what that involves on your side — and what doesn't apply to you.
1. There's nothing to set up on your Entra ID tenant
Regscribe authenticates through a single Microsoft app registration that already accepts sign-in from any Entra ID tenant (and personal Microsoft accounts). That means your employees sign in with their existing Microsoft work account through Regscribe's "Sign in with Microsoft" button, the same way they would for any other SaaS product — there is no SSO app to register, no redirect URI to configure, and no federation to set up on your end. You don't need to add Regscribe as an enterprise application in your own Entra ID admin center for it to work.
The access boundary that actually matters is Regscribe's own sign-in allowlist, not anything in Azure AD: an employee can only get in once their work email has been added to your company's allowlist by a Regscribe admin or your own company admin (see signing in). Being a valid user in your Entra ID tenant is necessary but not sufficient — they also need to be on that allowlist.
2. The one thing that might need your approval
Regscribe's Microsoft app registration is not yet a Microsoft-verified publisher. For most organizations this changes nothing — users just see an unverified-publisher notice the first time they sign in, same as countless smaller third-party apps, and can continue past it themselves.
If your organization has conditional-access or admin-consent policies that block unverified third-party apps outright, one of your employees may be stopped before they ever reach Regscribe's sign-in page, with a message from Microsoft (not Regscribe) saying the app needs admin approval. If that happens, it's a one-time action on your side: an Entra ID admin approves (grants consent to) Regscribe as an app for your tenant, from your own Entra ID admin center's enterprise applications / admin consent area. Once approved, every employee in your tenant can sign in normally — it is not something each individual user has to request.
3. What Regscribe requests
Sign-in only ever requests the standard identity scopes needed to know who someone is — their name, work email, and basic profile. Regscribe does not request access to your organization's files, mail, calendar, or directory as part of sign-in. (A separate, per-user, opt-in connector exists for browsing your own SharePoint/OneDrive files if you choose to use it — see the SharePoint connector guide for how that works and what it requests separately.)
4. Getting your team added
Email info@regscribe.ai with the work email addresses to add to your company's allowlist. If you want day-to-day control over who on your team has access without going through Regscribe each time, ask to have one of your team members made a company admin — they'll be able to invite and remove teammates from your company themselves, scoped only to your own company's team.