Skip to main content

Users, groups and email templates

Open Users or Groups after selecting a workspace. Create users administratively or let them register through your chosen authentication flow. The same email may exist in more than one workspace; always supply the intended client context when logging in or verifying a user.

Create and check a test user​

  1. Prepare the verification email template below in the intended workspace.
  2. For a no-app browser test, start the manual login test, choose registration on the hosted screen, and use an email you can access. This carries the client's settings through registration.
  3. Complete email verification when prompted, then sign in. If you already created the test user in this workspace, use that user's existing credentials instead of registering the email again.
  4. Check the Users list in the same workspace for the test email and its verification status. Complete the login/callback test to check that the account can sign in; a saved user record alone is not a login.

For administrative creation, use Users in the dashboard or the management request. If you need to explicitly assign oauth_client and the dashboard form has no client selector, that API request lets you supply the client directly.

If the email is missing from the list, check the selected workspace and filters. If the email already exists, continue with verification/login. If the message does not arrive, use email troubleshooting.

Organize users into groups​

Create a group in the selected workspace, then assign the intended users using the dashboard's group/user membership controls. Reopen the saved membership to check that the right users are included. Groups organize application users; inviting a developer to manage the workspace is a separate action on the workspace page.

User-list API requests support email filtering and limit/offset pagination. Profile changes and password changes are separate operations. Group membership uses the user and group IDs from the same workspace; developer workspace membership is unrelated.

Email templates​

Open Email templates. Templates belong to the selected workspace and need a name, subject and body. Supported names include email_verification, reset_password, registration_confirmation, welcome, workspace_invitation, magic_link, and new_device_alert.

For the first verification email, select Email Verification (email_verification), enter a subject such as Verify your email, paste the body below, and save. If that template already exists, review it rather than creating a duplicate. Saving a template stores the message format; it does not send an email.

Create email_verification before sending the first verification email. This body contains the code and its expiry:

Hello {{ first_name }},
Your verification code is {{ verification_code }}.
It expires in {{ timeout }} minutes.

For password recovery, create a separate template named reset_password with a subject such as Reset your password and this body:

Your password-reset code is {{ reset_code }}.
It expires in {{ timeout }} minutes.

Keep the double-brace variables unchanged. SyAuth generates the code and fills these values when it sends a message; you do not paste a real code into the saved template. verification_code belongs to email verification, while reset_code belongs to password recovery. Follow the verification and password-reset walkthrough to trigger and use the messages.

To check the template, trigger the matching action with your test user: registration/resend for verification, or password recovery for a reset. The mailbox should receive the message with a real code in place of the variable. Use that code in the matching verification or reset step. If the email still displays literal braces, check the template name, body and selected workspace.

Template names are unique within a workspace. The API accepts body or its html_content alias; conflicting values are rejected. Templates marked as default cannot be edited/deleted through the API. If a default template needs a change unavailable in the dashboard, contact support.

A successful user-create request does not prove email delivery. Verify the correct workspace/template, recipient address and spam folder, then request a fresh code. Report persistent failures with the workspace ID and request time. See email troubleshooting.

Use the user/group reference, template reference, and verification/reset endpoints for exact payloads.