GitHub
Team

Team

A team is a workspace with its own subdomain, members, and sites. Everything in BaseBlocks belongs to a team.

A team is the top-level workspace in BaseBlocks. It has its own subdomain, its own members, and contains all your sites.

https://your-team.baseblocks.dev

Every site, page, and document you create belongs to a team.

Team basics

Creating a team

When you sign up, you're taken to an onboarding page where you set up your first team. Enter a name and choose a slug — the slug auto-generates from the name.

The slug becomes the subdomain for all sites in the workspace. It must be lowercase and hyphen-separated.

Each account currently has one team. Support for creating and switching between multiple teams is planned for a future release.

Members and roles

Every team member has a role that controls what they can do.

RoleEdit pagesPublishManage membersManage settings
Admin
Member
Viewer

Admin — Full access. Can edit content, publish sites, invite and remove members, and change team and site settings. The user who creates the team is an Admin by default.

Member — Can edit pages and layouts in the editor. Cannot publish, invite others, or change settings.

Viewer — Read-only access to sites the team owns. Useful for stakeholders who need to review content without being able to change anything.

Inviting members

Open Team Settings → Members and enter the email address of the person you want to invite. They receive an invitation by email. Until accepted, the invitation appears as pending in the member list.

Invited users can be assigned any role at the time of invitation. The role can be changed at any time by an Admin.

Removing members

Open Team Settings → Members, find the member, and click Remove. They lose access to all sites in the workspace immediately.

What's next