Febasidocs

Workspaces

The container that holds your team's projects, members, and shared settings.

A workspace is the top-level container in Eved. Every project, every member invitation, every shared resource lives inside one. Organizations typically map one workspace to one product line or one team — projects within a workspace see and reference each other; workspaces are isolated from one another.

What a workspace holds

  • Projects of any type (Auth, Service, Application, Database, Automation, Integration).
  • Members with roles inside the workspace.
  • Settings: default project type, guest access, project-approval flow, notification preferences.
  • Branding: name, slug, optional logo.

The workspace slug appears in URLs and invitation links — pick it deliberately, it does not change easily.

Creating a workspace

From the sidebar, choose + New workspace. The form captures:

FieldRequiredConstraint
nameyes2–255 characters. Free-form human-readable label.
slugno2–100 chars; lowercase + numbers + hyphens. Auto-derived from name if omitted.
descriptionnoUp to 1000 characters.
logonoPublic URL to an image (PNG / SVG recommended).

The user who creates the workspace becomes its owner.

Members

A workspace member has one of three roles:

RoleCan
ownerEverything — including transferring ownership and deleting the workspace.
adminManage projects, invite members, change workspace settings.
memberView projects and contribute according to per-project permissions.

Workspace-level roles are independent of the RBAC roles inside an Auth project — that is its own system, see Authorization.

Settings worth knowing

  • Default project type — chosen when a member uses + New project; saves clicks for teams that mostly create the same type.
  • Guest access — when on, lets externally invited collaborators view selected projects without becoming members.
  • Project-approval flow — when on, project creation requires admin/owner approval before provisioning.

What's next

On this page