Team & Workspaces
Organize BladePDF access around a workspace, invite collaborators, assign roles, and manage the shared identity used across the dashboard.
The workspace boundary
A workspace is the shared boundary for your team, plan, templates, assets, API keys, webhooks, render history, analytics, and stored PDFs. The workspace control in the dashboard header identifies the workspace and plan you are currently using.
When a template, API key, render, or stored PDF appears to be missing, confirm that the dashboard is showing the expected workspace before changing configuration.
Members and invitations
Open Team in the dashboard to invite a member and review active, pending, or disabled access. The member list shows each person's role, status, and join date, with search and role filters for larger teams.
- Select Invite member.
- Enter the teammate's email address and choose the smallest role that fits their work.
- Review pending invitations from the Team page.
- Change or disable access when responsibilities change.
Roles and permissions
BladePDF provides Owner, Admin, Member, and Viewer access levels. The permission matrix on the Team page is the source of truth for what each role can do across workspace settings, billing, renders and analytics, templates and assets, API keys, webhooks, and support.
| Role | Typical use |
|---|---|
| Owner | Workspace ownership and the most sensitive workspace-level actions. |
| Admin | Day-to-day administration across the workspace and its integrations. |
| Member | Operational work with the product without full administrative control. |
| Viewer | Read-oriented access for stakeholders who do not manage resources. |
Workspace settings
The Team page also contains shared workspace settings such as its name, URL slug, and logo. These values identify the workspace across the dashboard, so use a stable organization or product name rather than an individual environment name.
Ownership transfer and workspace deletion are kept in the danger zone and may be restricted by workspace type or the current member's permissions.
Recommended access practices
- Give each person their own account instead of sharing credentials.
- Use the least-privileged role that supports the person's responsibilities.
- Review pending and disabled members during regular access audits.
- Keep API keys scoped to integrations and environments; do not use a person's dashboard credentials in application code.
- Remove access promptly when a teammate or contractor leaves.