Product
Teams & Collaboration
Use Qorlivo workspaces, roles, invites, and activity history to collaborate without sharing one account.
Teams help multiple people manage links, videos, domains, profiles, analytics, and developer settings in the same workspace.
When to use a team workspace
Use a team workspace when:
- More than one person creates or edits links.
- A marketing, support, sales, or content team needs shared visibility.
- You want billing and usage tied to a shared workspace.
- Developers need API access for a company account.
- You need a clear activity history for changes.
Roles
Qorlivo roles control what each teammate can do.
| Role | Typical access |
|---|---|
| Owner | Manages billing, workspace settings, team members, and all resources. |
| Editor | Creates and edits workspace content such as links, videos, collections, and profile content. |
| Viewer | Reviews resources and analytics without making broad changes. |
Choose the lowest role that still lets the person do their job. You can update roles later if responsibilities change.
Invite teammates
- Open Settings.
- Go to Team.
- Enter the teammate's email.
- Choose a role.
- Send the invite.
- Ask the teammate to accept from their email or invite link.
If the invite expires or is revoked, send a fresh invite.
Seats
Plans include different seat limits. If a teammate cannot join, check:
- Whether the invite is still valid.
- Whether the workspace has an available seat.
- Whether billing needs an upgrade.
- Whether the teammate is signing in with the invited email.
Collaboration habits
- Use clear link titles so teammates can understand resources quickly.
- Add campaign resources to collections.
- Review activity history when something changes unexpectedly.
- Use roles instead of sharing credentials.
- Revoke access when someone leaves the team or project.
- Keep API keys owned by the workspace, not by one person's laptop or notes.
Activity history
Activity history helps answer what changed and when. It can include events such as resource creation, updates, deletion, team changes, API key changes, webhook changes, and billing-related actions.
Use activity history when a link destination changes, a webhook stops behaving as expected, or a teammate needs context for recent updates.