Overview

In this use case, you may be an MSP (Managed Service Provider) using Skeddly for your customer/client, and you want to allow your client into the Skeddly account so they can access their actions.

In this case, you do not want your client to access actions for other clients.

Instructions

Step 1: Create one or more projects for each of your clients. Each project should be dedicated to one client.

Step 2: Create one or more managed users for your client.

Step 3. On each user created in Step 2, give them only "Basic" role. This allows them only basic Skeddly functionality, such as changing their own username & password. With only the "Basic" role assigned, a user cannot access any projects.

Step 4: On each user created in Step 2, for each project they should have access to, give them any of the following roles, depending on the desired access level:

  • Admin - Complete access to the project, including project settings.

  • Standard - Complete access to the project, but not including changing project settings.

  • Read-Only - Read-only access to the project. Meaning, they can see all actions, Managed Services plans, credentials, etc. But they cannot modify anything.

  • Execute Actions Only - Read-only access to the project. But they can execute existing actions.

  • Manage Action Exclusions - Read-only access to the project. But they can create/modify action exclusions.

The user will not be able to access (or even see) any projects that don't have permissions assigned.

Did this answer your question?