2. Invite team members

~4 minute read. Get your teammates in, with the right level of access, in about five minutes.

Step 2: Settings → Members

Go to https://app.eworks.cloud/settings/members. You'll need the Admin role.

[Screenshot: Members table with role dropdowns and an Invite people button]

Roles

Rules of thumb: your platform team are Admins, everyone doing daily work is a Member, and auditors, security reviewers, and finance are Viewers. Roles are enforced server-side on every request — the UI hides what you can't do, but the API is what actually decides.

The invite flow

1. Click Invite people.
2. Paste one or more email addresses (comma or newline separated — up to 50 at a time).
3. Pick a role for the batch. You can change any individual's role later.
4. Optionally add a short note; it's included in the email.
5. Click Send invitations.

Your teammate receives an email, clicks the link, signs in or creates an account at id.eworks.cloud, sets up MFA, and lands in your workspace. Invitations expire after 7 days; you can resend or revoke from the Pending tab at any time.

# Same thing from the API
curl -X POST https://api.eworks.cloud/v1/workspaces/$WORKSPACE_ID/invitations \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email":"bob@company.com","role":"member"}'

{
  "id": "inv_01J8Z...",
  "email": "bob@company.com",
  "role": "member",
  "status": "pending",
  "expires_at": "2026-09-15T08:30:00Z",
  "invited_by": "usr_01J7A..."
}

Automatic provisioning (optional)

Bigger teams skip invitations entirely:

• Domain join — anyone with a verified @company.com address joins as a Member automatically.
• SCIM 2.0 — Okta or Entra ID pushes joiners, movers, and leavers. Deprovisioning is immediate: the session is revoked on the next request.
• Group-to-role mapping — map an IdP group to Admin, Member, or Viewer, and stop managing roles here at all.

Both live under Settings → Authentication. See the e.identity docs for the full setup.

Team audit log

Every membership change is recorded: who invited whom, when the invitation was accepted, every role change, and every removal. Filter the audit trail by action type member.* to see it, or open Settings → Members → Activity for the same events scoped to this page.

Troubleshooting

"The invitation email didn't arrive." Check spam first, then the Pending tab — if the status is Delivered, it left our side. Ask IT to allow no-reply@eworks.cloud and the sending domain. You can also copy the invite link from the row's menu and send it over Slack; the link carries the same single-use token.

"I can't see my team members." You're probably in the wrong workspace — check the switcher in the avatar menu. Viewers see the member list read-only; Members see names but no controls.

"How do I remove someone?" Settings → Members → <user> → Remove. Their sessions die immediately, agents they own keep running but are reassigned to you, and their chats stay in the workspace (they're workspace data, not personal data) unless you also run a data deletion request. Removal is irreversible and, of course, logged.

Next: Your first chat message