Workspace Overhaul: roles, permissions & shared usage

Every workspace starts with three roles: Admin, Operator and Viewer. You can create your own, rename, re-order and delete them.

Each role has a set of permissions:

• How they act in the workspace; anything revolving a workspace and what they can do, which includes but not limited to, starting a chat, sandbox, viewing analytics or any sort of logs...
• How they act on servers; if they can even see a server and add it to their chats, read or edit files, reading server memory or running console commands

Each server can give or take away permissions for a role or a single member, on that server only. For example, an Operator can edit files on your test server but only read them on survival.

Admins can make Conny ask before doing a certain action such as editing files, deleting or moving files, running commands and so on... and this can be forced for the whole workspace, just a server, for a role or a member even. This means that Conny would always ask, no matter what, before executing an action like editing files or running commands.

An owner or an admin can choose whether server access through Conny is shared or personal

• Shared; When an owner adds a server, anyone can add that server to their chat if they have the permission for it
• Personal; When an owner adds a server, every member will have to enter their own credentials before having access to that server in the chat

Members can share part of their plan usage with the workspace pool, and anyone can add extra usage to the workspace from their own account.

• Choose which roles may spend the pool and the workspace's extra usage, and override that for single members.
• Usage is always taken in the same order: the workspace pool, your plan, the workspace's extra usage, then your own extra usage.
• Each member can switch off the sources they'd rather not use.

Every change to members, roles, servers, logins, GitHub, approvals and spending is written to the workspace's activity log.