Managing users and roles
Quick answer
Go to Account → Users in the Portal sidebar to invite and manage your organisation's members. You see this item if your role grants User Management access, for example Administrator, Owner or User Manager.
Access is organised around your organisation's members and the roles they're given, managed from Account → Users.
Invite someone
Log in to Portal
Go to portal.worldstream.com.
Open Account → Users
The sidebar shows this item if your role grants User Management access, for example Administrator, Owner or User Manager.
Click "Invite user" and fill in their details
Their email address, first name and last name.
Give them one or more roles
A member can hold more than one role, so you can cover a mix of responsibilities that no single role covers on its own. For exactly what each role grants, area by area, check the permissions table further down this page before you invite.
Send the invitation
They'll receive an email to set up their own account, and appear in your Users list once they've done so.
Users
Account → Users
| Name | Roles | Status | Actions | |
|---|---|---|---|---|
| Account Owner | owner@example.com | Owner | ACTIVE | … |
| Finance Contact | finance@example.com | Finance | ACTIVE | … |
| Ops Team Member | ops@example.com | Operations | ACTIVE | … |
Managing an existing member
The Users list shows each member's Name, Email, Roles and Status, with an Actions column at the end of the row. Change which roles a member holds from there. A role change propagates to that member within about a minute. After that, anything they no longer have access to stops showing in their sidebar, and a direct API call returns an access-denied response rather than partial data.
Roles
Roles are not a fixed list. Each role is a named bundle of permissions, one setting per feature area, each set to None, Read (view-only) or Write (view and change). Administrator and Owner are protected roles: they always exist, have write access everywhere, and cannot be edited or deleted. Every other role can be edited, deleted, or created from scratch with any mix of None, Read and Write per area, so you can shape access around how your own team is organised.
The table below is one real example configuration, to show what a set of roles looks like in practice. Your own account may have different role names and different permissions, so check Account → Users for what applies to you.
| Role | User Mgmt | Billing | Account | Verification | Compute | Network & Security | Backups | Object Storage | Kubernetes | Developers | Support | Datacenter Services |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Administrator * | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write |
| Owner * | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write | Write |
| Development | None | None | Read | None | Write | Write | Write | Write | Write | Write | Write | Write |
| Finance | None | Write | Write | None | None | None | None | None | None | None | None | None |
| Network Engineer | None | None | None | None | Read | Write | None | None | Read | Read | Write | Write |
| On-site access | None | None | Read | None | Write | Write | Write | Write | Write | Write | Write | Write |
| Operations | None | None | Read | None | Write | Write | Write | Write | Write | Write | Write | Write |
| Platform Engineer | None | None | None | None | Write | Write | Write | Write | Write | Write | Write | Write |
| Read-only Auditor | Read | Read | Read | Read | Read | Read | Read | Read | Read | Read | Read | Read |
| Support | None | None | Read | None | Write | Write | Write | Write | Write | Write | Write | Write |
| Support Engineer | None | None | None | None | Read | Read | Read | Read | Read | Read | Write | Write |
| System Engineer | None | None | None | None | Write | Read | None | None | None | None | None | None |
| User Manager | Write | None | Write | None | None | None | None | None | None | None | None | None |
- = protected role: always present, full access, cannot be edited or deleted.