# Onboarding Users to OneLens

## Overview

To ensure **secure and role-appropriate access** across your organization, OneLens requires all  other team users to be **explicitly added by an Admin user**. Without this setup, team members cannot sign in or interact with the platform.

Through the following setup you can also:&#x20;

* **Control** over who has access to OneLens.
* **Align permissions** with user roles and personas.
* Maintain **organizational governance** over their cost visibility and actions.

{% hint style="warning" %}

## NOTE

Only users with the **"Admin"** user type can add or manage other users in OneLens. Make sure you log in with an **admin account**.
{% endhint %}

## Adding a  New User

{% stepper %}
{% step %}
**Log in with Admin Access**

Sign in to [OneLens UI](https://app-in.onelens.cloud/) using an email that has **admins privileges.**
{% endstep %}

{% step %}
**Go to User Settings**

* Click **Settings** in the left sidebar.
* Under the **Organization** section, select **User Settings**.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FjY8aG8rvqleS9zGgiy4G%2FScreenshot%202025-06-03%20at%2012.55.03.png?alt=media&#x26;token=2040cd79-914a-4d8e-9c22-d250f0a72fda" alt="" width="563"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Create User**

The user list appears displaying all the current users along with their status (**Active, Inactive**). Click the **Create User** button located at the top right.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2F2RgLNYWcaMNK9D0A6FBr%2FScreenshot%202025-06-06%20at%2011.30.24.png?alt=media&#x26;token=a2ac9167-c493-4667-8613-13eae2af26d9" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Select User Type**

* **Admin**: Has full platform access and can change organization-wide settings.
* **Member**: Has limited access to specific cost centers with assigned roles.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FVQdOzotsVzvMi4Vm0Qgf%2FScreenshot%202025-06-06%20at%2011.33.50.png?alt=media&#x26;token=d22e0f16-a71c-418c-9eed-079d164437dc" alt="" width="375"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Enter User Details**

* &#x20;Enter the user email address, first name and last name.
* Choose the User persona (e.g FinOps Owner, Developer, DevOps Owner)
  {% endstep %}

{% step %}
**Assign Cost Centers (Member User Only)**

For members type, select one or more cost centers the user can access.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FiBwKIqJ5uiGct3vNs4fC%2FScreenshot%202025-06-06%20at%2011.37.38.png?alt=media&#x26;token=b29163f3-06ea-4087-aa56-81cd1a4d2231" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}

## **Understand Your Cost Center Hierarchy First**

Before assigning, ensure you’re familiar with how cost centers are structured in your organization. This determines what data and actions the user can access.

You can also **view or modify the cost center hierarchy** anytime by going to **Settings → Business Mapping Cost → Organization Cost Center**.
{% endhint %}
{% endstep %}

{% step %}
**Confirm the Creation**

Click **Create** to send out a confirmation mail to the user.&#x20;
{% endstep %}
{% endstepper %}

## What Happens After

* Once the user is created, their status updates to **Active**.
* The user can then log in to the OneLens platform.

{% hint style="success" %}
[**Read the login guide**](https://docs.onelens.cloud/getting-started/accessing-onelens) to learn how users can access their account.
{% endhint %}

## Managing Existing User Access

You can view and take actions on any user—whether they are **Active or** **Inactive** state.

{% stepper %}
{% step %}
**Open User Settings**

Navigate to **User Settings** via the **Settings** menu.
{% endstep %}

{% step %}
**Find Users**

Use the **search bar** or **status filters** to locate the user.
{% endstep %}

{% step %}
**Access User Actions**

Click the **three horizontal dots** at the end of the user's row to open the menu.&#x20;

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FCKQxKSquR4KtsuyzVja3%2FScreenshot%202025-06-06%20at%2011.43.41.png?alt=media&#x26;token=700fa31f-a131-4aaa-af57-160990a888c3" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Choose Action**

* **Revoke Access**: Deactivate the user immediately.
* **Edit Access**: Modify user role, persona or access level as per cost centers.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2Fg48zOUp9CskZHyOVwoyo%2FScreenshot%202025-06-03%20at%2013.04.06.png?alt=media&#x26;token=1c36208c-7bba-489a-9aac-ee50d7080433" alt="" width="375"><figcaption></figcaption></figure>

{% endstep %}
{% endstepper %}

## **Access Revocation: Impact & Recovery**

Revoking a user’s access deactivates their account immediately. The user's status will change to **Inactive**.

Once revoked:

* The user will no longer be able to log in.
* Their profile will remain visible with an **Inactive** status.

  <figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FVGUyhEU5pKaocWrDiL0X%2FScreenshot%202025-06-03%20at%2013.06.13.png?alt=media&#x26;token=6faedbd9-b667-4df7-ba29-a11d09354b7d" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}

## Reactivating User Access

If access needs to be restored later, follow these steps:

* Open the **three-dot menu** next to the user's row in the User Settings table.
* Click **Re-activate**.
* The user's status updates to **Active**, and their previous access and roles are reinstated.
  {% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.onelens.cloud/getting-started/onboarding-users-to-onelens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
