Coda Tutorial for Planning & OKRs

Explore

Coda Tutorial for Planning & OKRs

Coda Tutorial for Planning & OKRs

3. Run the process

3.2 Sharing with your company

Updating sharing settings to make sure the right people have access.

You’ve locked down the doc! That means the time has come to get your doc out to the world your company! Let’s talk through how to share your planning doc with your company and how to bring a few co-builders in to help you maintain it.

⁠

⭐ What you’ll get

A planning doc that’s been distributed to your company

💼 What you’ll use

Sharing

⁠

1. Define your permissions.

When sharing the doc with your team, you’ll want to think about permissions.

Types of sharing in Coda:

Viewers cannot edit the doc. At most, they can make a copy the doc or request editor permissions to make changes.

Commenters are basically the same as the viewers except they can add comments to the doc.

Editors can edit pages to the extent that page locking allows. If they don’t have page unlocking permissions on the doc, they won’t be able to make any non-permitted edits.

Bonus: Who should be an editor?

Anyone who contributes to your planning and execution process should be an editor. Specifically, if an employee will be contributing to the writing, editing, or updating of OKRs they should be able to do so unhindered, beyond page locking.

Here at Coda, most of our OKR doc is unlocked and everyone is an editor. However, all our employees have a lot of training with the product.

For your initial rollout, get the other planning leaders together, walk them through the doc and how to unlock pages. Invite them to the doc and give them page unlocking permissions.

In case you are worried about accidental changes, know that you can use doc history to mitigate incorrect modifications. Check out

@Help! we lost data?! Someone deleted a row / a cell / a page / a table / ...⁠

⁠

A good OKR process has potentially everyone helping write OKRs, updating notes, etc. Because of this, editors permission is more appropriate for your colleagues than viewers or commenters.

You probably want everyone in your organization to be able to add OKRs, updates, notes, etc. That means, you will need to make everyone an Editor, but you can restrict the edits they can make on the pages themselves. By locking individual changes, you can be sure they can not make fundamental changes such as deleting tables or changing instructions. They will have reduced permissions based on the default locking settings we have established in

3.1 Locking down a doc⁠

Additionally, you might want a few people besides yourself to be able to make infrastructural changes in this document such as building additional functionality or fixing issues that come up. This group should be able to freely unlock all pages as defined in

3.1 Locking down a doc⁠

2. Sharing the doc.

Share with your company.

In top right of your doc, click Share.

From here, you can invite specific individuals as viewers or editors. Additionally, you can make it accessible to anyone within your workspace. If you’d prefer to control access beyond this, you can also move the doc into a folder that only a certain group of people can access.

Read more here.⁠

⁠