> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/user-onboarding/balkanid-onboarding.md).

# BalkanID onboarding

1. **Enter organization name:**
   1. Navigate to **app.balkan.id**.
   2. Enter the organization name as configured in BalkanID.
   3. The system redirects to the organization’s **Login / Sign-up** page.

{% hint style="info" %}
If the organization name is unknown, contact the organization's BalkanID administrator or the BalkanID support team.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/v6KU0zNJerP7JV59oHTq" alt=""><figcaption></figcaption></figure></div>

2. **Signing into BalkanID:**\
   There are two ways to sign into BalkanID depending on how your admin has configured the environment. They are :
   1. Use your SSO provider to login (Okta, Microsoft, Ping etc.) for a seamless experience by using an existing Identity Provider (IdP).
   2. Sign up using social providers (such as Google) or magic link on the BalkanID Application (if a social provider hasn't been set up on your tenant yet).
3. **Role-based access**

   Once your account has been verified, your admin will assign a role to you in BalkanID. We have 3 primary roles used on our application which have been listed below. Depending on the role assigned to you, the following tabs will be visible:

   1. **Reviewers**: A users with this role will be able to view the *My tasks*, *Access Requests*, *Account* and *Help* menus. Reviewers will be able to review Access requests and perform the tasks assigned to them by the other roles.
   2. **Risk managers**: A user with this role will be able to view the *Entities*, *Summary*, *Campaigns*, *Access Reviews* and all other menus that a Reviewer has access too. Risk Managers will be able to discover application, people, connection and identity entitlements as a reviewer. They can view the various campaigns and perform access reviews as a part of this role. In addition they can perform all the tasks a Reviewer can perform as well.
   3. **Administrators**: A user with this role will be able to view the Settings and all the other menus that a Risk Manager has access too. Administrators will be able to control the settings. This includes adding user employee data, integrating applications, viewing all application entitlements in one place, manage rules and saved filters and finally configure system notifications.
4.

For specific assignment of roles based on your business needs, please refer to the following help link: [User Role Management](/getting-started/setting-up-your-tenant/user-role-management.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/getting-started/user-onboarding/balkanid-onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.