How to create a shared workspace for your team
In this short guide you’ll learn how to:
- Create a shared workspace
- Invite your team and share secrets with them
- Upgrade to a paid subscription
In this guide we assume that you have installed the SecretHub CLI and created an account. To do so, you can follow these two simple steps:
Step 1: Create a shared workspace
To collaborate with team members, you need a shared workspace.
To create one, run the
org init command:
secrethub org init
You will be asked to type in a name for your organization. Pick something short and recognizable, e.g. your company name.
Similar to your personal workspace, you can create repositories in a shared workspace. Create one now, you will use it later to share secrets with your team:
secrethub repo init your-company/start
Let’s add a few directories and secrets to the repository so we have something to share:
secrethub mkdir your-company/start/dev echo "Hello Development" | secrethub write your-company/start/dev/hello secrethub mkdir your-company/start/prd echo "Hello Production" | secrethub write your-company/start/prd/hello
Step 2: Invite your team
It’s no fun working alone, so let’s invite some team members. SecretHub user accounts are personal accounts that are not tied to a single organization. This means that your team members need to have created an account before you can invite them to your organization.
For the purpose of this guide, let’s say your teammate Alice signed up with the username
Now that you have a friend on SecretHub, you can invite her to your organization workspace using the
org invite command:
secrethub org invite your-company alice
Next, let’s invite Alice to collaborate on the
secrethub repo invite your-company/start alice
Finally, to instantly share all
dev secrets with Alice, you can create an access rule:
secrethub acl set your-company/start/dev/ alice read
Alice can now read all secrets in the
your-company/start/dev directory, including the
secrethub read your-company/start/hello
Under the hood all the encryption has been taken care of.
To allow her to also write to the
dev directory, change the access rule to
secrethub acl set your-company/start/dev/ alice write
With the access rule in place, she can now both read the secret and write a new version of it.
Naturally, this is only a small subset of what you can do with shared workspaces but you get the gist. Kick the tires for a bit, invite more team members and check how this could work for you.
You’ve now covered the bases of managing your organization within SecretHub.
To learn more, check out these resources:
Finally, to get your organization back to a clean state, you can remove the
start repository used in this guide by running:
secrethub repo rm your-company/start
And you’re done. Happy coding!
How to upgrade to a paid subscription
To upgrade your SecretHub organization to a premium plan, you have to login to the dashboard.
If you signed up through the CLI, press the
Signed up through the CLI button to request a password for the dashboard.
After choosing a password and signing in, you can switch organizations on the left of the navigation bar. Select the organization that you would like to upgrade and you will see the current plan attached to the organization on the bottom right.
To upgrade, press the
Purchase button and select the plan that you would like to purchase.
Next, enter your credit card details and provide your billing information when requested.
Confirm it, and you’re done! Now you can enjoy all the features you used during the trial.