Projects and Collaboration
Projects provide multi-tenant isolation boundaries in Omnismith. All data models (Attributes, Templates, Entities), Automations, Dashboards, and Access Security settings live inside a specific project workspace.
1. Project Operations & Context Switching
Section titled “1. Project Operations & Context Switching”- Project Switcher: Use the project dropdown in the top left header to switch between accessible project workspaces.
- Creating Projects: Project owners can create new empty projects or initialize workspaces from Marketplace Blueprints.
- Project Settings: Customize the project name, description, and default timezone.
2. Managing Team Members & Role Assignments
Section titled “2. Managing Team Members & Role Assignments”- Navigate to Project Settings → Users (or open Project Details from the sidebar).
- Invite Member: Click + Invite Member and enter the email address of the team member.
- Assign Role: Select a predefined role (e.g. Owner, Admin, Editor, Viewer) or a custom workspace role.
- Member Offboarding: Remove members or modify their role permissions at any time.

💡 Developer Architecture Note
Section titled “💡 Developer Architecture Note”[!NOTE] Strict Multi-Tenant Isolation: Every API request carries a
X-Project-Idcontext header. Database queries and Kafka event queues are scoped strictly to the project tenant, preventing cross-tenant data leakage.
Next Steps
Section titled “Next Steps”[!TIP]
- Configure granular access rights in Roles & Permissions.
- Manage active user login sessions in Sessions.