Choose where you work and see what your role opens
Switch the project in the header, manage the projects of the organization in the settings and see what each role opens.
4 min read
Everything in Slen belongs to an organization, and most of it to one of the projects of that organization. This page says how the two fit together, how to move between them in the console and what each role sees.
Organizations and projects
An organization is your company in Slen. A project is a part of it that a service works in: an API key belongs to one project and acts in that project only.
| Belongs to | What |
|---|---|
| The organization | The members and the invitations, the audit log, the name, the currency and the time zone |
| One project | The API keys, the flows, the operations and the customers |
| A project or the whole organization | A connection, a provider pool, a policy, a budget and an alert rule. You choose which when you create one |
A new organization starts with one project.
What is created for the whole organization applies to every project. Only a member who reaches every project creates or changes such a thing.
Switch the project or the organization
The header of the console shows where you work: the organization, the project and, at the end, your role in the organization. Most pages show the data of that project. With no project in reach the header shows the organization and your role.
1. Open the switcher
Press the name in the header. The panel shows the organization with your role in it, and the active projects you reach.
2. Choose a project
Press a project. The page you are on is read again for that project. A long list has a search field.
3. Go to another organization
Press All organizations, then press an organization in the list. The console opens it on the project you worked in last.
Your organizations
Organizations is the page you land on after you sign in. It lists the organizations you are a member of, with your role in each, and the invitations that wait for you.
Press Create organization to start a new one. It takes a name, a currency and a time zone, and you become its owner. A person can be a member of several organizations and have a different role in each.
The name, the currency and the time zone are changed later on Organization, by an owner or an admin.
Manage the projects
Open Settings, then Projects. The page lists the projects you reach, each with its environment, its time zone and its status. The project you work in is marked Current.
An owner or an admin creates a project with Create project. A project has a name, a time zone and an environment — Development, Staging or Production. The menu in the row of a project holds the rest.
| Action | What it does |
|---|---|
| Make current | Switches the console to the project, like the switcher in the header |
| Edit | Changes the name, the environment, the time zone, the description and the status |
| Deactivate | Takes the project out of the switcher. The project stays in this list, and Activate brings it back |
Deactivating a project does not revoke its API keys.
What each role opens
A role is a set of permissions — the same permissions an API key has. Authentication says what each permission includes.
| Role | Permissions | In the console |
|---|---|---|
| Owner | management:write, gateway:write | Reads and changes everything. Only an owner makes another member an owner |
| Admin | management:write, gateway:write | Reads and changes everything, except the membership of an owner |
| Developer | management:read, flows:write, gateway:write | Builds and publishes flows and sends requests. Reads the settings and the budgets and changes neither |
| Finance | management:read, read | Reads every section and the settings. Changes no settings |
| Viewer | read | Reads Overview, Operations, Budgets, Alerts and the model catalogue |
The menu shows only the sections your role reads, and Settings shows only the cards whose pages it opens. The address of a page your role does not read leads to Overview, with a message that says why.
Access to projects
Besides the role, a member has a project access: All projects or Selected projects. An owner and an admin always reach every project. A developer, a finance member or a viewer reaches every project or only the ones selected for them.
A member with selected projects sees those projects only — in the switcher and in every list. Such a member reads what belongs to the whole organization and cannot change it, and does not open the audit log.
Where to go next
Members and invitations — invite a person, give a role and choose the projects.
Manage API keys — the keys of a project.
Glossary — the terms of this page in one place.