Skip to content

Workspaces and Namespaces

The application defines a hierarchy to organize your data and manage access control efficiently. This structure consists of two main levels: Workspaces and Namespaces.

Workspaces

A Workspace is the top-level container for your organization. It represents your company or team environment.

  • Access: When you log in, you are authenticated into a specific workspace. If your email is associated with multiple workspaces, you will be asked to select one during the login process.
  • Scope: User management and global settings are typically handled at the workspace level.
  • Global Resources: Some resources, like Schemas, are shared across the entire workspace. This promotes consistency, allowing different teams to share standard data definitions.

Namespaces

Namespaces are logical subdivisions within a workspace. They act as distinct containers for your configurations (Figs), allowing you to isolate different projects or teams.

Creating a Namespace

To create a new namespace:

  1. Click the Namespace Selector in the navigation bar.
  2. Select + Create new (or the equivalent "Add" button) from the dropdown menu.
  3. Enter a unique name for your namespace.
    • Note: Namespace names should start with a letter and contain only lowercase letters, numbers, and hyphens.
  4. Click Create Namespace.

Switching Namespaces

You can switch between namespaces at any time using the Namespace Selector in the top navigation bar.

  • Selecting a different namespace will immediately update the Figs view to show only the configurations belonging to that context.
  • Your currently selected namespace persists as you navigate through the application.

Managing a Namespace

You can edit settings specific to a namespace by clicking the Edit icon (pencil) next to the namespace name in the selector dropdown. This opens the Edit Namespace dialog, which acts as a control panel for that specific context.

The dialog provides the following tabs:

  • General:
    • Assign User: Grant other users access to this namespace specifically.
    • Roles: Assign specific permissions (e.g., Admin, Editor, Viewer) to control what users can do within this namespace.
    • Client Tokens: Generate tokens that allow external applications or CI/CD pipelines to programmatically read configurations from this specific namespace.
  • Data Dictionary:
    • Maintain documentation specific to this namespace. This is useful for documenting domain-specific terms or configuration rules that don't apply to the entire workspace. The data dictionary will improve the accuracy of AI suggestions when creating schemas, because it will understand the domain-specific terms you've documented.