Operate
Team & access
Invite your team, and decide which projects each person can see or change.
Owners and admins invite people from Team in the dashboard. Each invite is a one-time link that expires after 7 days. The person opens it, sets their name and a password, and is in. Kardlane doesn’t email the link: copy it and send it to them yourself, and only to them.
Roles#
| Role | Can |
|---|---|
| Owner | Everything, including billing and managing other owners. |
| Admin | Everything except managing owners: every project, WhatsApp numbers, billing, org settings and the team. |
| Member | Only the projects they’re given, at one level each (below). No WhatsApp numbers, billing, org settings or team. |
Project levels (members)#
| Level | Can |
|---|---|
| View | See the project: trades, timelines, vendors and settings. Read only. |
| Operate | Also resolve trades, message vendors, pause or stop the bot on a trade, and accept or decline re-quotes. |
| Manage | Also change the project’s settings, vendors, routing, integration (API keys, webhook) and alerts, and switch its bot on or off. |
A member doesn’t see projects they weren’t given anywhere in the dashboard, and their support requests are their own or about their projects.
Changing and removing access#
- Changes apply on the person’s next click; they don’t need to sign out.
- Removing someone signs them out straight away. Everything they did stays in trade timelines and logs.
- Nobody can change their own access, only an owner can make or change an owner, and an org always keeps at least one owner.
- A new link for an invite replaces the old one; cancelling an invite makes its link stop working.
- One email belongs to one organization. To join a second one, use a different email.
Your API keys belong to a project, not a person, so they keep working when people come and go.