Setting up access control on Skycap
If you are working in a team, you will probably need to control who has access to Formations, and how much they can do with that access (i.e. their permissions). This guide walks you through the process of creating and maintaining access control policies in Skycap Formations.
What you’ll need
Before you start, please check you have the following:
A Cloud 66 Account — If you don't already have one sign up for a Cloud 66 account. Your first server is free, no credit card required.
An existing application set up in Skycap — You can learn how to do that with our Getting started with Skycap guide.
An existing Formation defined in Skycap — You can learn how to do that with our Getting started with Skycap Formations guide.
At least two team members on Cloud 66 (including yourself) — You can add team members using the Teams section of the Account Settings interface.
Overview
Skycap supports two interrelated security policies for Formations and Stencils: Access control which defines which assets a user can access Permissions which defines what the user can do with that access
Creating a Formation access policy for a user
In order to set up an access policy for a Formation within any application:
- Open your Cloud 66 dashboard and click on the name of the application in question.
- Click on Formations in the left-hand nav
- Hover your mouse next to the edit icon for the Formation in question - a small padlock icon will appear. Click it.
- Under the first section (permissions for the specific Formation in the specific app), click the “+ Add Permissions for a user” button
- Select the user in question from the dropdown and check any of the boxes to permit that user to perform those actions.
- Click the Save Permissions button
You can repeat steps 4 - 6 to add policies for any number of team members.
Giving users higher levels of access
If you’d like to give team members permissions to edit all of the Formations in one application, or all the Formations in all of your applications, you can simply follow the steps above, but add the user’s permissions to the second or third section, respectively.
Creating a Stencil access policy for a user
In order to set up an access policy for a Stencil within any application:
- Open your Cloud 66 dashboard and click on the name of the application in question
- Click on Formations in the left-hand nav
- Click on the name of the Formation which contains the Stencil in question
- Hover your mouse next to the edit icon for the Stencil in question - a small padlock icon will appear &emdash; click it
- Under the first section click the “+ Add Permissions for a user” button
- Select the user in question from the dropdown and check any of the boxes to permit that user to perform those actions.
- Click the Save Permissions button
Editing or revoking access
In order to edit an existing access policy for any Formation:
- Open your Cloud 66 dashboard and click on the name of the application which contains the Formation.
- Click on Formations in the left-hand nav Hover your mouse next to the edit icon for the
- Formation in question - a small padlock icon will appear. Click it.
- Find the user in question and add or remove permissions by checking or unchecking the appropriate boxes.
- Click the Save Permissions button
You can revoke a user’s access completely by following the above steps but, at Step 4, clicking on the red delete icon to the right of that user’s entry in any section.
You can do the same for any Stencil by first navigating to the Formation in which it lives, then clicking the padlock next to that Stencil, and then following steps 4 & 5 above.
What’s next?
- Learn how to update an existing service in Skycap.
- Learn how to add new services or components to a service.
- Learn how to roll back to an older version of your application using Snapshots.
- Learn how to add custom environment variables to your application.
- Learn how to use your Habitus build flow within Skycap.
- Learn how to use validation policies to ensure your Stencils adhere to your standards and conventions.