> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/identity-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/identity-support/user-guide/organization-admin-app/become-an-oten-developer.md).

# Become an Oten developer

The **Become an Oten developer** feature allows an organization administrator to enable the **Developer Portal** for specific workspaces in the organization.

After the Developer Portal is enabled for a workspace, the **Workspace administrator** of that workspace can access the Developer Portal. The **Workspace owner** can also adjust permissions to grant Developer Portal access to workspace members when needed.

***

### When to use this feature

Use this feature when your organization wants to:

* Enable the **Oten Developer Portal** for one or more workspaces.
* Allow Workspace administrators to access the Developer Portal in enabled workspaces.
* Allow Workspace owners to manage Developer Portal access for workspace members.
* Start integrating internal systems or apps with Oten Identity, Oten Workspace, or the Oten Store.

***

### Access permission

Only users with the required administrative permission in Oten Admin can enable the Developer Portal for workspaces.

After the Developer Portal is enabled for a workspace:

* Workspace administrator will have access to the Developer Portal.
* Workspace owner can adjust permissions to grant Developer Portal access to workspace members.
* Workspace members can access the Developer Portal only after they are granted the required permission.

***

### How to enable the Developer Portal for workspaces

{% embed url="<https://app.supademo.com/demo/cmr0gwh8r11kkqm4ib39duaix?utm_source=link>" %}

#### Step 1: Open Become an Oten developer

In Oten Admin, go to the left sidebar and select **Become an Oten developer?**

The **Become an Oten developer** popup will be displayed.

#### Step 2: Review the introduction

At the top of the popup, you can review why enabling the Developer Portal is useful.

The Developer Portal helps your organization:

* Integrate with **Oten Identity**.
* Build and manage secure apps on Oten.
* Publish apps to the **Oten Store**.
* Provide developers with workspace-based tools and access.

#### Step 3: Select workspaces to enable

In the **Enable workspaces** section, select one or more workspaces where you want to enable the Developer Portal.

You can:

* Select a workspace using the checkbox at the end of each row.
* Use **Select all** to select all workspaces in the list.
* Use **Clear all** to remove all selected workspaces.
* Use the search box to find a workspace by name.

The number of selected workspaces is shown above the list, for example: **1/3 selected**.

#### Step 4: Confirm the change

After selecting the workspaces, select **Confirm** to save the change.

If the **Confirm** button is disabled, check that:

* At least one valid workspace has been selected.
* The selected workspace has not already been enabled for the Developer Portal.
* You have the required permission to perform this action.

***

### Result after enabling the Developer Portal

After the Developer Portal is enabled successfully:

* The Developer Portal becomes available for the selected workspace.
* The Workspace administrator of that workspace can access the Developer Portal.
* The Workspace owner can adjust permissions to grant Developer Portal access to workspace members.
* Workspace members can access the Developer Portal only after they are granted the required permission.
* The enabled workspace will appear in the workspace context or workspace switcher on the Developer Portal for users who have access.

***

### Notes

* Enabling the Developer Portal is applied per workspace. It is not automatically applied to the entire organization unless all workspaces are selected.
* If your organization has multiple workspaces, only enable the Developer Portal for workspaces that need app development or integration capabilities.
* Workspace administrators will have access to the Developer Portal after the workspace is enabled.
* Workspace members do not automatically get Developer Portal access.
* Workspace owners need to adjust permissions if they want to grant Developer Portal access to workspace members.
* If a user does not have Developer Portal access in the current workspace, they cannot use developer features in that workspace.