Skip to main content
Smerio organizations have two roles: Administrator and Member. A role applies to one organization. Switching organizations uses your membership and permissions in that organization. The person who creates an organization starts as an Administrator. Invitations sent from Smerio also default to Administrator. Select Member when a colleague should work with messages without managing the organization.

​
What each role can do

The Hub currently uses simulated messaging. A role grants access to the available features. It does not enable production sending. Billing actions are not available yet.

​
Invite colleagues

  1. Open Getting started and complete your company setup.
  2. Find Invite your team, the optional onboarding step.
  3. Enter your colleague’s email address.
  4. Keep Administrator for full organization access, or choose Member for message access without administration.
  5. Select Send email invitation.
You can select Skip for now and return later. From Workspace settings → Team, select Invite colleagues to return to this step. Invitations expire after seven days. Refresh the pending invitation list to check its current state, or select Revoke to cancel an invitation that has not been accepted. A pending invitation does not grant organization access. Clerk handles the invitation email and acceptance flow for both new and existing accounts. After joining, the colleague can select the organization from the Menu → Organization selector. An invitation being created does not confirm that its email was delivered or accepted.
Invite your team form with a fictional email address, Member role and pending invitation

Optional invitation form and pending list in a local synthetic workspace. The identity provider is simulated. No email is sent.

​
Manage the team

The Team panel in Workspace settings is visible only to administrators. It lists current members and their roles, with pagination and a Refresh team action.
Team settings listing an administrator and two members with role and access controls

Running Team panel with synthetic members. These screenshots do not demonstrate hosted sign-in or changes to real accounts.

​
Change a role

  1. Find the person in Workspace settings → Team.
  2. Select Administrator or Member.
  3. Select Save role and review the confirmation.
  4. Confirm the change.
Changing someone to Administrator grants team, configuration and API-key management. Changing them to Member keeps message access and removes organization administration permissions.
Confirmation explaining the access granted when Jamie Chen becomes an administrator

Review the person and the effect of a role change before confirming. Synthetic local example.

​
Remove access

  1. Find the person in Workspace settings → Team.
  2. Select Remove access.
  3. Review the confirmation and confirm the removal.
The person loses access to this organization. Shared messages and company data stay in the organization, and the person can be invited again later. Removing organization access does not delete their account or memberships in other organizations. Organization API keys are managed separately. Removing a person’s membership does not revoke shared organization keys. An administrator can revoke those keys when needed.

​
Keep an administrator

Every organization must retain at least one administrator. Smerio blocks attempts to remove or demote the last administrator, including simultaneous changes through the Hub’s team API. Promote another member before stepping down or removing the current administrator. A pending invitation does not count as an administrator. If you change your own role or remove your own membership, the Hub reloads to apply your new access.
Mobile Team panel showing the last administrator protection and instruction to promote another member first

The last administrator's role and removal controls are disabled, including on mobile. Synthetic local example.

​
How access is enforced

Permissions are checked by the API using the current organization membership, so hiding a button is not the only protection. Members cannot bypass these checks by calling an administrative endpoint directly. Only Administrator and Member are supported. An unknown organization role is rejected. Team updates also check that the person’s role still matches the one shown when you started editing. If another administrator changed it first, refresh the team and review the latest role before trying again. API keys use their own limited scopes. They are not organization member roles and cannot manage team membership, even if they can access messaging endpoints.

​
Troubleshooting

  • Team is missing: check that you selected the intended organization and have the Administrator role.
  • You cannot change or remove an administrator: promote another member first if this is the last administrator.
  • The role changed while you were editing: select Refresh team and review the updated member list.
  • A request fails or its result is unclear: refresh before retrying. A failed response does not always mean the provider rejected the change.
Open Workspace settings or contact support.