Design schemas as a team
Relmic is built for teams. Create organizations, invite members, assign roles, and control who can view and edit your database schemas — with full audit logging for accountability.
Organizations
An organization is the top-level container for team collaboration in Relmic. All team projects, members, and settings live within an organization.
Creating an organization
- Open the organization switcher in the dashboard sidebar.
- Click Create Organization.
- Name your organization and select a plan.
- Invite your team members by email.
Organizations require an Organization or Enterprise plan with a minimum of 3 seats. View plans.
Team management
Within an organization you can create teams to group members by function — for example, “Backend”, “Data Engineering”, or “Platform”. Teams can be granted access to specific projects, so each group only sees the schemas relevant to their work.
Invitations
Invite members by email from the organization settings. Each invitation includes a role assignment. Pending invitations are visible in the members list and can be resent or revoked at any time.
Roles and permissions
Relmic uses role-based access control with three roles. Each role determines what a member can see and do within the organization.
Admin
Full control over the organization. Can manage members, teams, billing, and all projects. Can lock and unlock projects.
- ✓Create and delete projects
- ✓Invite and remove members
- ✓Manage teams and roles
- ✓Lock and unlock projects
- ✓View audit logs
- ✓Manage billing
Editor
Can design and modify schemas within projects they have access to. Cannot manage organization settings or members.
- ✓Edit schemas (tables, columns, relationships)
- ✓Create revisions and milestones
- ✓Export and import schemas
- ✓Create and promote drafts
Viewer
Read-only access to schemas. Can view diagrams and export code but cannot make changes. Ideal for stakeholders and reviewers.
- ✓View schemas and diagrams
- ✓Export schemas (read-only)
- ✓Browse revision history
- ✓View visual diffs
Editor seats and viewers
On the Pro plan, you can add editor seats to your personal account. Each editor seat allows one additional person to edit your schemas. Viewers are always free and unlimited.
On Organization plans, all seats include full editor access. You pay per seat, and every member can edit schemas based on their role.
Project locking
Project locking prevents any edits to a schema. This is useful for production schemas that should not be changed without a formal review process.
- Only Admins can lock and unlock projects.
- Locked projects are read-only for all members, including editors.
- A locked project displays a lock icon in the dashboard and editor.
- You can still view, export, and browse revisions of a locked project.
Use locking in combination with drafts to enforce a design review workflow — lock the main schema, work in drafts, and promote changes only after approval.
Audit logging
Every action in an organization is recorded in the audit log. This includes:
- Schema changes (who changed what, and when)
- Member management (invitations, role changes, removals)
- Project lifecycle events (creation, deletion, locking)
- Export and sharing events
Access the audit log from the organization settings. Logs are searchable by member, project, and date range. Audit logging is available on Organization and Enterprise plans.