# Concepts

CloudSigma AI Studio resources are organized by region and workspace. Understand these boundaries before you store endpoint, credential, or resource identifiers in an application.

## Regions are independent deployments

Each CloudSigma region contains an independent control plane and data plane. It also maintains its own accounts, resources, and billing records. Select a region first, then use that region's console and API endpoint for every operation in the same workflow.

For example, `mnl2` identifies the Manila 2 region in the Philippines. Its console origin is `https://genai.mnl2.cloudsigma.com`, and its AI Studio API base URL is `https://genai.mnl2.cloudsigma.com/v5`.

Do not combine an API endpoint from one region with a workspace ID or credential from another region. If your organization uses more than one region, keep a separate configuration for each region.

## Workspaces and the object hierarchy

A [workspace](https://omnifabric.cloudsigma.com/docs/guides/ai-studio/resource-center/workspace.html.md) is the main governance boundary for resources; it holds members, roles, data, workflows, and compute resources. You usually obtain and use object IDs along this hierarchy:

```text
Workspace
├─ Members (linked to user accounts) and roles
├─ Catalog → database → table or volume → file
├─ Connector → import task → import run
├─ Workflow → workflow job → artifacts and data lineage
├─ Knowledge base → knowledge sources and semantic configuration
├─ Agent → session or automation task → agent artifacts
└─ Compute instances, data publications, and data subscriptions
```

## Easily confused concepts

**Definitions and run instances.** A [workflow](https://omnifabric.cloudsigma.com/docs/guides/ai-studio/processing/workflow.html.md) definition, an import task, and an automation task are long-lived objects; a workflow job, an import run, and an agent task are run instances produced on each trigger. Saving or deploying only updates the definition — it does not mean anything has run. A successful submission does not mean execution finished: save the run instance ID and query its status and result. Deleting a definition or task does not roll back data already written.

**User accounts and workspace members.** A user account is the platform-level login identity; a workspace member is that account's membership in a workspace, with a role and tags (see [User Management](https://omnifabric.cloudsigma.com/docs/guides/ai-studio/permissions/users.html.md)). Removing a workspace member only ends that workspace relationship — it does not delete the platform account.

**Data publications and data subscriptions.** With [Data sharing](https://omnifabric.cloudsigma.com/docs/guides/ai-studio/resource-center/share-data.html.md), one workspace publishes a database for others; another workspace then sets up access to it (see [Data subscriptions](https://omnifabric.cloudsigma.com/docs/guides/ai-studio/resource-center/subscribe.html.md)). Deleting a subscription does not delete the source data; before deleting a publication, check existing subscriptions and downstream dependencies.

## Next steps

- Make your first request: see [Make your first AI Studio API call](https://omnifabric.cloudsigma.com/docs/developer/quickstart/index.html.md)
- Choose a task: see [API](https://omnifabric.cloudsigma.com/docs/developer/api/index.html.md)