Roles & permissions
A role is a named set of permissions. Each person in your organization has one role. You manage roles in Organization → Roles: give the role a name, then tick its permissions.
Launch and strategy permissions
| Permission | In plain words |
|---|---|
launch.read | See your launch page, business identity and brand kit. People with this permission also get the daily email about new items that need attention. |
launch.write | Act on the launch: press I've done it — check now, Ask Spark to do it, edit your business identity and brand kit, and finish launch setup. |
verification.documents | See and download verification documents. Uploading or deleting a document also needs launch.write. People without it do not see the documents area at all. |
strategy.read | See your strategy, its versions and the monitor. |
strategy.write | Answer and edit the strategy steps, ask for suggestions, start the monthly review. |
strategy.approve | Approve the strategy, or withdraw an approval. |
Rolling out
The three strategy permissions come with the strategy workspace, which is being rolled out now.
Who has them at the start
- Your organization's top admin role gets all six permissions automatically.
- Other roles get none of them until an admin adds them.
Suggested set-ups
- Owner or manager: all six.
- Marketing helper:
launch.read,launch.write,strategy.read,strategy.write. They can prepare everything; the owner approves. - Viewer:
launch.readandstrategy.readonly. - Give
verification.documentsonly to people who must handle official papers.
TIP
Spark staff can see your launch so they can help, but they can never approve your strategy for you.