Onboarding support and troubleshooting

Use this page for customer questions and troubleshooting related to starting with Yarken, completing onboarding, setting up the first administrator, preparing tenant access, and helping new users sign in successfully.

General onboarding

Q: What are the prerequisites before starting Yarken onboarding?

A: You need:

An active Azure subscription
A Microsoft Entra ID (Azure AD) tenant
A user with Global Administrator or Application Administrator role in Azure

These permissions are required to approve the Microsoft consent request and configure the Yarken Enterprise Application. See Initial Yarken administrator setup above for the full setup steps.

Q: Which onboarding model should I choose?

Scenario	Recommended model
Small team, administrators want direct control over user access	Direct user management
Enterprise environment using Azure AD for identity governance	Microsoft Entra ID role management

If your organization already manages application access through Microsoft Entra ID groups and app role assignments, the Azure AD model is recommended. If you prefer manual, invite-only control, use direct user management.

Q: Can I switch between onboarding models after initial setup?

A: Yes. Navigate to Admin → Settings → Tenants and update the Invite Only and Azure AD Roles toggles. Refer to the recommended tenant configurations for the correct combination. Switching models does not delete existing users, but you should review role assignments afterward to ensure access is governed correctly.

Q: What role does the first Yarken administrator receive?

A: The first administrator provisioned by the Yarken team receives the Admin role with full platform access — including user management, settings, and all functional areas. For a complete list of roles, see Users.

Q: The Microsoft consent invitation link is not working or has expired. What should I do?

A: Consent links can expire or fail if the link was already used, the Azure session timed out, or browser cache is interfering. Try:

Clear browser cache and cookies, then reopen the link
Use a private or incognito browser window
Ensure you are signed in with the correct Azure administrator account
If the link has expired, contact support@yarken.com for a new invitation

Q: The consent request shows "Need admin approval." What does this mean?

A: This appears when a non-admin user attempts to approve the consent request. Only users with Global Administrator or Application Administrator roles in Azure can approve. Ask your Azure administrator to approve directly via Microsoft Entra ID → Enterprise Applications → Yarken. See Integrate Microsoft Entra ID (Azure AD) for details.

Q: Does Yarken store or manage user passwords?

A: No. Yarken uses Microsoft authentication (OpenID Connect) for login security. Passwords are managed entirely by your identity provider (Microsoft Entra ID). Yarken does not store, manage, or have access to user credentials.

Tenant configuration

Q: What happens if Invite Only and Azure AD Roles are set incorrectly?

A: Misconfigured tenant settings are one of the most common sources of onboarding issues. Use the correct combination:

Onboarding model	Invite Only	Azure AD Roles
Manual user management in Yarken	Enabled	Disabled
Microsoft Entra ID role management	Disabled	Enabled

Incorrect combinations can cause users to be unable to sign in, sign in without roles, or have Azure AD role assignments ignored. To review or update, navigate to Admin → Settings → Tenants and click Edit. See Configure tenant access and domain controls.

Q: Why can't users from my organization domain sign in automatically?

A: If Invite Only is enabled, users must be manually added by an administrator before they can access Yarken — even if they belong to the same domain. To allow automatic domain-based sign-in, disable Invite Only in Admin → Settings → Tenants. Users who sign in automatically will still have No Role until an administrator assigns one.

User access and roles

Q: A user can log in but sees no menus, dashboards, or data. Why?

A: The user has authenticated successfully but has not been assigned a Yarken role. Users with No Role cannot access any dashboards or functional areas. To resolve:

Navigate to Admin → User Management → Users
Find the user and assign an appropriate role (Admin, Power User, Viewer, etc.)
If using Azure AD, verify the user's app role assignment in Microsoft Entra ID → Enterprise Applications → Yarken → Users and Groups

See Users for the full list of roles.

Q: A user has a role but still cannot see entity-specific data. What's wrong?

A: Non-admin users require entity access in addition to a role. Without entity access, Yarken displays an entity access error. To assign:

Navigate to Admin → User Management → Entity Access
Select the user
Move required entities from Available Entities to Assigned Entities
Click SAVE

Access takes effect immediately. See Entity Access.

Q: How do I onboard multiple users at once?

A: Yarken supports bulk user upload via CSV:

Download the Users template from the Data Dictionary
Populate Name, User Name, Email, and Roles (separate multiple roles with a comma)
Navigate to Admin → User Management → Users → click UPLOAD
Drag or drop the CSV file and review validation results

Users uploaded without a role are assigned No Role by default. See Add users.

Q: How do I deactivate a user without deleting their account?

A: Set the user's status to Inactive in Admin → User Management → Users. Inactive users remain in the system but cannot sign in, and can be reactivated later. See Add users directly in Yarken platform.

Azure AD integration

Q: Azure AD role changes are not reflected in Yarken. Why?

A: Role changes in Microsoft Entra ID take effect only on the user's next sign-in. The user must sign out and sign in again. Also verify that Azure AD Roles is enabled in Admin → Settings → Tenants — if disabled, Yarken ignores Azure AD role assignments. See Integrate Microsoft Entra ID (Azure AD).

Q: Can I use Azure AD groups to assign Yarken roles instead of individual users?

A: Yes. For enterprise environments, create security groups in Azure AD (e.g., Yarken-Admin, Yarken-PowerUser, Yarken-Viewer), add users to the groups, and assign groups to the Yarken Enterprise Application with the corresponding app role. See Integrate Microsoft Entra ID (Azure AD) for step-by-step group setup.

Troubleshooting onboarding issues

For core troubleshooting (user cannot access Yarken, consent approval errors, user can log in but cannot access data).

User receives "Access Denied" when signing in

Cause: The user's domain is not registered in the Yarken tenant, or Invite Only is preventing automatic access.

Resolution:

Navigate to Admin → Settings → Tenants and verify the domain matches the user's email domain
If Invite Only is enabled, manually add the user via Admin → User Management → Users
If the domain is missing or incorrect, contact support@yarken.com

Bulk user upload fails validation

Cause: The CSV file has formatting issues, missing required fields, or invalid data.

Resolution:

Verify the file uses the correct template from the Data Dictionary
Ensure Name, User Name, and Email are populated for all rows
Separate multiple roles with a comma (e.g., Power User, Budget Contributor)
Review row-level validation errors displayed during upload

See Add users for template guidelines.

Cause: The user has a role but no entities assigned. Non-admin users require at least one entity.

Resolution:

Navigate to Admin → User Management → Entity Access
Assign at least one entity to the user
Click SAVE — the user can retry login immediately

See Entity Access.

Users assigned through Azure AD not appearing in Yarken

Cause: The user hasn't signed in since being assigned, or Azure AD Roles is disabled.

Resolution:

Verify Azure AD Roles is enabled in Admin → Settings → Tenants
Confirm the user is assigned to the Yarken Enterprise Application in Azure AD with a valid app role
Ask the user to sign in — user details are captured on first authentication
If using groups, verify the group is assigned to the Enterprise Application

See Integrate Microsoft Entra ID (Azure AD).

Licensing or feature access issues after onboarding

Cause: Yarken features (Analytics, Planning, Ask Yarken, etc.) are controlled by licensed entitlements, not just roles.

Resolution:

Verify the active license covers the required modules in Admin → Settings
If uploading a license, use the .lic file format and confirm the subscription is active
Contact your Yarken account representative or support@yarken.com

See Licensing and feature access.