# Workspaces ### Scope This document explains how **Workspaces** function within the organizational structure and how administrators create and manage them. *** ### I am new. Where should I start? #### What is a Workspace? A **Workspace** is a logical boundary inside an organization used to group: * Users * Resources * Configurations * Access permissions Workspaces define **where access is scoped** and **where work happens**. *** #### How Workspaces fit into the organization At a high level, the structure looks like this: `Organization ├── Workspace A ├── Workspace B └── Workspace C` * An organization can have multiple workspaces * Users can belong to one or more workspaces * Access is always evaluated in the context of a workspace *** #### Why Workspaces exist Workspaces help organizations: * Separate projects, products, or environments * Isolate access between teams * Apply security policies at a smaller scope than the entire organization * Delegate administration safely *** #### When should you use Workspaces? Use Workspaces when: * You manage multiple projects or teams * You need to isolate environments (Dev / Staging / Production) * Different groups require different access rules Note\ Small organizations may start with a single workspace and expand later. *** ### I already understand. How do I proceed step by step? #### Step 1: Open Workspace Management * Sign in to the Admin Console * Navigate to [Oten Workspace](https://workspace.oten.live/more-spaces) * Select **Workspaces** *** #### Step 2: Create a New Workspace * Click **Create Workspace** * Enter a workspace name (required) * Optionally add a description to clarify its purpose * Click **Create workspace** *** #### Step 3: Manage Workspace Profile After the workspace is created, you can manage its basic information from **Workspace profile**: * Update **Workspace name** * Update **Description** (optional) * View **Workspace code** (read-only, used for identification) Changes are applied immediately and affect all users within the workspace. *** #### Step 4: Manage Access and Membership From **Access management**, control who can access the workspace: * Add users → Navigation **Individuals → Add individuals** * Remove users → Navigation **Individuals** * Organize users into **Groups :** Add group and Management group
**Note** :\ \- View members\ \- Manage roles\ \- Remove Group * Assign **Roles and permissions** scoped to the workspace : Create Role and Delete role
Access changes take effect immediately. *** #### Step 5: Configure Workspace Resources Within the workspace, administrators can manage: * Applications and integrations * Subscription and marketplace apps * Workspace-specific configurations and settings All resources created here are isolated to this workspace. *** #### Step 6: Review Activity and Audit Logs Use **Activity log** to: * Track workspace-level changes * Monitor administrative actions * Support auditing and security reviews --- # 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://oten.gitbook.io/identity-support/user-guide/business-account/business-owner-default-authority/organizational-structure/workspaces.md?ask= ``` 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.