Sign in to FactVerse

Use this page when onboarding a user or validating that an account can enter the correct FactVerse environment. The same identity foundation supports web console access, product clients, field workflows, and authenticated API experiences, but the exact login URL and available products depend on the customer deployment.

Before you start

Item	Check
Environment URL	Use the URL provided by the project or tenant administrator. Cloud, private cloud, and on-premises environments can use different domains.
Account status	Confirm the user has been invited or created, and that the account is active.
Sign-in method	Confirm whether the tenant uses password login, enterprise SSO, or a deployment-specific method.
Tenant membership	Confirm the user belongs to the correct tenant, project, site, or organization.
Product access	Confirm the role package includes the product area the user needs.

Inputs

Prepare these inputs before the first login test:

Input	Example
User identity	Name, email, enterprise username, or expected identity claim.
Environment	Production, staging, private cloud, or on-premises URL.
Sign-in method	Password, SSO, product client login, or deployment-specific entry.
Tenant target	Tenant, project, site, or organization the user should enter.
First task	View an asset, open a document folder, inspect a connector, or start a workflow.

Sign-in flow

Steps

1. Open the FactVerse environment URL provided for the project.
2. Choose the sign-in method configured for the tenant.
3. Complete password login or the enterprise SSO redirect.
4. If prompted, select the tenant, project, or site where the work will happen.
5. Open the target product area, such as Inspector, DFS, ECM, Designer, or AI Agent.
6. Confirm the user can perform the expected first task, such as viewing an asset, opening a document folder, checking a connector, or entering a workflow.

First-login validation

Run a small validation before declaring the account ready.

Validation	Expected result
Environment	The browser or client opens the correct customer environment.
Identity	The displayed user name, email, or identity claim matches the expected person.
Tenant	The user sees the correct tenant or project.
Navigation	Only relevant product areas are visible.
Product task	The user can complete the first task required by the role.
Audit	The sign-in and first access appear in the expected administrative or audit view when available.

Client considerations

Some product clients have their own login screens or deep links. When a user can sign in on the web console but cannot sign in through a client, confirm:

• the client is pointed to the same environment;
• the client version supports the tenant's sign-in method;
• the device has network access to the identity provider and FactVerse environment;
• browser pop-up, redirect, or embedded web view restrictions are not blocking SSO;
• the user's product package includes the client they are trying to use.

Handoff checklist

• User can sign in with the configured method.
• User can select or enter the correct tenant.
• Product navigation matches the role.
• The first product task has been tested.
• Any access exceptions have an owner and approval record.

Expected result

At handoff, the user should know which environment to open, which sign-in method to use, which tenant to select, and which first task confirms that access is ready. The tenant administrator should have enough evidence to distinguish a future login failure from a product permission issue.

Related pages

• Use Enterprise SSO when the tenant redirects to an enterprise identity provider.
• Use Users, Roles, and Permissions when the user can sign in but cannot see the correct product area.
• Use Authentication Troubleshooting when login fails or loops.