Share this page

# Space-Workspace hierarchy

Spaces are the contexts in which an ALM Octane user can work, depending on permissions.

Spaces are containers for workspaces. For details on workspaces, see About workspaces.

Site admins can create spaces.

Space admins manage spaces. The space admin can associate workspaces to a space, define users, and set API access.

Some entities are defined on the space level, such as users or API keys.

The space admin can create the following types of spaces: Isolated and shared.

Isolated spaces

The space admin can define users and API access.

Each workspace associated with an isolated space has its own set of data, which only admins for the workspace and assigned space admins can customize.

The Isolated icon indicates the space is isolated, and when displayed next to an entity, indicates that the entity is not shared across workspaces.

Shared spaces

The space admin can define users and API access.

Additionally, the space admin can customize data to be shared across workspaces (Enterprise Edition).

Shared entities include items like releases, epics, user-defined fields, forms, and calendars.

The Shared icon indicates the space is shared, and when displayed next to an entity, indicates that the entity is shared across workspaces.

Some entities can be customized both for shared spaces (affecting all associated workspaces) and also for individual workspaces. Only the admin for workspaces and assigned space admins can customize entities for their individual workspaces.

Shared spaces
Customizable for shared spaces only, affecting all associated workspaces | Customizable for all workspaces associated with a shared space, and also for individual workspaces | Customizable for individual workspaces only
--- | --- | ---
List items Space calendars API access | Releases and milestones Workspace calendars Forms Rules Users User-defined fields (UDFs) Workflow | Teams Team calendars Programs

Example

There are three development divisions in your company: Hardware, Software, and Internal.

The hardware, and its accompanying software, must be released on the same release schedule and are made publicly available. Even though processes for these two divisions' deliverables might be different, the release schedule is the same. Also, a subset of testers test both hardware and software.

Internal development activities are on a different schedule and have nothing in common with the other two divisions' activities.

- Enterprise Edition: Create a shared space called External_Deliverables.

- Enterprise Edition: In the shared space External_Deliverables, create a workspace called Hardware and a workspace called Software. These workspaces will share releases and users.

- Create an isolated space called Internal_Deliverables. Create an Internal workspace in this space. The workspaces in this space do not share information with any other workspaces.

- Enterprise Edition: Create programs for the Internal, Hardware, and Software workspaces. Examples of programs you might create for the Software workspace could be MyAppWeb and MyAppMobile.

Tip: For strategies to set up your spaces and workspaces, see Best practices for setting up spaces and workspaces.

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ValueEdge & ALM Octane Help Center ValueEdge ALM Octane Help 16.0.100-16.0.400 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: