> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity.md).

# Workspace & Identity

Workspace & Identity defines who can access BuildingPro Suites, what they are allowed to do, and how the working environment is organized for them.

This area of Platform Core brings together user administration, role-based permissions, tenant-related access structure, tags, and start-page behavior. It ensures that the right people see the right data and functions in the right context.

## What You Can Manage Here

This section includes:

* [Users](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/users.md) for creating and managing user accounts
* [Roles](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/roles.md) for defining system-wide and tenant-specific permissions
* [Tags](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/tags.md) for structuring access and classification
* [Start Page](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/home-page.md) for defining the user entry experience

## Why It Matters

Workspace & Identity is what turns a technically working platform into a usable operational environment. It allows administrators to assign responsibilities, limit access where needed, and keep collaboration structured across teams, tenants, and stakeholders.

Together with Asset Core and Governance & Monitoring, it provides the organizational layer of Platform Core.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
