Enterprise registration
Register a new enterprise tenant, configure single sign-on, and give the first administrator a company portal URL.
Who this is for
The person who will own the PlexArch tenant for your organization. You need OAuth credentials from Google, Microsoft Entra ID, or ADFS before you finish the form.
How to open the form
From the public home page, choose Get Started. You can also go directly to:
/EnterpriseRegistration/Register
If you already have an account, use Company login instead.
What you provide
Enterprise information
| Field | Required | Notes |
|---|---|---|
| Enterprise name | Yes | Up to 100 characters. Becomes the tenant display name. |
| Enterprise address | No | Up to 500 characters. |
| Authentication provider | Yes | Google, Microsoft Entra, or ADFS. |
Authentication provider configuration
Select a provider, then complete the matching block. Credentials are stored with the enterprise so users can sign in later.
- Client ID and Client Secret (required)
- Redirect URI (optional)
- Scopes (default:
openid,email,profile)
Microsoft Entra
- Tenant ID, Application (Client) ID, and Client Secret (required)
- Redirect URI (optional)
- Authority URL, for example
https://login.microsoftonline.com/{tenant-id} - Scopes (default:
openid,email,profile)
ADFS
- ADFS URL and Relying Party ID (required)
- Client ID and Client Secret (required)
- Redirect URI and scopes (optional)
Admin user information
| Field | Required | Notes |
|---|---|---|
| Full name | Yes | First administrator. |
| Designation | Yes | Role title, for example IT Manager. |
| Email address | Yes | Used for the confirmation email and later company login. Must belong to the selected identity provider (Gmail cannot be used with Microsoft Entra or ADFS). |
| Phone number | Yes | Valid phone format. |
You must accept the terms and privacy policy before submitting.
What happens on submit
- PlexArch creates the enterprise and the admin user in a single transaction.
- A unique company URL is generated from
ApiUrls:EnterpriseLoginplus the new enterprise ID. - A confirmation email is sent to the admin with the company URL. If email delivery fails, registration still succeeds.
- You are redirected to the success page.
If validation or save fails, the form redisplays with an error. Fix the fields and submit again.
After registration
The success page shows:
- Enterprise name, address, and company URL
- Admin name, designation, email, and phone
- A copy button for the company URL
- Access Dashboard (opens the company URL)
- View All Enterprises (registration list)
Share the company URL with people who should sign in to this tenant.
Company login
Use this when you already registered and need the portal.
- Open
/EnterpriseRegistration/CompanyLoginor Sign In. - Enter the work email registered for the tenant.
- Choose Access Company Portal / Continue to Login.
PlexArch looks up the enterprise from that email, then checks that the address belongs to the identity provider configured for that tenant before sending you to Google, Microsoft Entra, or ADFS. For example, a Gmail address cannot sign in to a Microsoft Entra or ADFS tenant, and a personal Outlook/Hotmail address cannot sign in to a Google tenant. Custom work domains (for example you@company.com) are allowed for the provider that enterprise registered.
If the email is not registered, you see “This email is not registered for an enterprise.” If the address does not belong to that provider, you see that the email does not belong to the configured identity provider.
From a company URL (/enterprise/login/{enterpriseId}), enter the matching work email. PlexArch still resolves the enterprise from the email and requires it to match the URL, then continues with that tenant’s identity provider. The email returned by the provider must be the same registered address, and the provider used (Google, Microsoft Entra, or ADFS) must match the enterprise configuration.
From the company login page you can also start a new registration.
Next steps
After you can sign in:
- Invite users and assign roles under Company.
- Load architecture data with Onboarding.
- Seed standard compliance checklists.