Permissions & access

Namespaces

A namespace is your workspace on CloudWady. It holds your projects, servers, backups, team and billing. Everyone you add to it gets an access level in it, and that level decides what they can see and do there.

The top bar always shows the namespace you are working in. When you belong to more than one, click it to open the switcher:

• Click a name to work in that namespace alone.
• Tick the boxes next to several names to see them together.
• Click the icon to work in a namespace and every client namespace below it.

Each row shows how many projects the namespace holds. A Sandbox badge marks the shared demo you see after signing up, and Pending marks a namespace CloudWady has not reviewed yet.

Client namespaces

An agency can keep each client in a namespace of its own, below the agency's. A client namespace has its own projects, members and billing.

To add one, go to Overview and click Add Client Namespace above your projects. You fill in the client's name, contact email, VAT number and address, then click Create & Open Client.

The button is available when all of these are true:

• you are an Admin of the namespace you are working in;
• the namespace has an active White Label add-on;
• at least one of its projects is approved and on a paid plan;
• you are not working in the Sandbox.

When one is missing, hover the button to see which.

Members of the agency's namespace reach its client namespaces with the same level. In Team & Access they show there as Inherited. A level given to someone on the client namespace itself takes precedence over the inherited one.

Access levels

There are five levels. Each includes everything the levels above it in this table can do.

By environment

What you may do to an app depends on the environment it runs in. The same rule applies in the dashboard, the API, cw and AI assistants.

A server that hosts a production app counts as production for the terminal, whatever else runs on it.

Team & Access

Team & Access lists your namespace and the client namespaces below it as a tree, each with its members. A namespace you belong to but do not administer is marked View only.

Each namespace's row shows its seats in use against its total, the Add seats button and the Add member button. Each member's row shows their name, email and level, and the Deactivate button.

Two filters add the members hidden by default:

• Inherited shows the members whose access comes from a parent namespace.
• Deactivated shows the people you took off a namespace.

To find someone, type in the search box at the top of the screen. It searches every namespace in the tree.

Click the arrow at the start of a row to open that member's details:

• their notification settings (see below);
• when they last signed in;
• where their access comes from;
• which other namespaces they belong to.

Add a member

Click Add member on the namespace's row. Then choose one:

• Select Existing User for someone who already has a CloudWady account;
• Create New User for anyone else. Enter their name, login and email. Leave the password empty and they get an email to set their own.

Pick their Access Level and confirm. If you typed a password instead (the key button generates one), pass it on to the person in a safe way; they can change it under My Settings Profile.

Every active member of a namespace uses one of its seats. Members who only inherit access from a parent namespace use none here. If the namespace has no free seat, CloudWady refuses to add the member: add seats or move a project to a plan with more of them.

Change a level

Pick a new level in the member's row; it applies straight away. An admin can give any level in the namespaces they administer, Admin included. An inherited member's level is changed in the namespace it comes from.

Lowering a level also removes SSH access the new level does not allow:

• Down to Developer: the member's SSH keys on servers that host production apps are removed.
• Down to Viewer: all their SSH keys on the namespace's servers are removed.

Deactivate a member

Deactivate takes the person off this namespace. Their SSH keys on its servers are removed, and their seat is freed. Their access to any other namespace stays as it was. The Deactivated filter lists them, with a Restore button to bring them back.

A member marked Account disabled can't sign in anywhere on CloudWady. Contact support if you think that is a mistake.

Notification settings

Each membership has its own notification settings. Open a member's row to see them. You can change your own, and an admin can change anyone's in the namespaces they administer.

What each alert is and where it is sent is covered in Alerts & notifications.

Account review

CloudWady reviews new sign-ups. Until then, the member's row shows Pending review. A pending account works normally. A Rejected account can't sign in. You don't need to do anything about either. Contact support with any question.