# Core concepts

A few key concepts shape how everything on the platform fits together. You don't need to memorise these — but skimming them now will save you confusion later.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-sitemap" style="color:$primary;">:sitemap:</i></h4></td><td><strong>Workspaces &#x26; projects</strong></td><td>The two main containers — and how they relate to each other.</td><td></td></tr><tr><td><h4><i class="fa-lock" style="color:$primary;">:lock:</i></h4></td><td><strong>Permissions</strong></td><td>Who can do what, and how access flows from workspace to project.</td><td></td></tr></tbody></table>

***

### The mental model in 30 seconds

You sign up and get an **account**. Your account belongs to one or more **workspaces**. Each workspace contains **projects**. Members are invited to a workspace and given a role; that role determines what they can do across all projects in that workspace.

That's it — the rest is detail.


---

# 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://sunwin88vipcom.gitbook.io/sunwin88vipcom-docs/documentation/core-concepts/core-concepts.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.