Your member account identifies you as an individual. A workspace defines the scope of team collaboration. Enter the correct workspace before working with accounts, messages, or tickets.
Sign-in and your personal account
Depending on site configuration, the sign-in page offers password or email verification-code sign-in. Server settings determine whether registration, password recovery, and invitations are available. Email verification requires an email service. If a code does not arrive, check the email address, spam folder, and resend interval before contacting your site administrator.
Go to Settings → Profile, then select Edit profile and account security to open your personal account page. You can update your display name and time zone and change your password. Changing a password requires the current password; the new password must be 12–128 characters. A successful change signs you out of every session, so you must sign in again.
Your personal time zone and the workspace's default time zone are separate settings. Interpret team schedules and reports in the context of the workspace time zone.
Create or switch workspaces
On the workspace selection page, enter a name and default time zone, then select Create and enter. Names must be 1–100 characters. The creator becomes the owner.
If you belong to multiple workspaces, use the workspace switcher in the sidebar. A suspended workspace or membership may prevent access. Ask the owner to check; do not create a replacement workspace for the existing team.
Invite members
- Open Settings → Workspace and members, then expand Seats and team members.
- If you have invitation permission, open Invite team member.
- Enter the recipient's email address or user identifier, as supported by the page, and choose their role.
- Enter your own member sign-in password when asked to confirm.
- Copy the newly generated invitation link and share it with the intended recipient. The link is only shown when it is generated.
- After the recipient signs in with the matching identity, reviews the invitation, and accepts it, check the member list.
Sites with email verification disabled only support invitations by user identifier. If an invitation has expired, was revoked, or does not match the recipient's identity, ask the inviter to check it. Unused invitations can be revoked from the invitation list.
Ordinary members still need Telegram account grants after joining a workspace. Configure the invitation role and account permissions separately.
Roles and member management
| Role | Meaning |
|---|---|
| Owner | The person who created the workspace; can transfer ownership when permitted |
| Administrator | Manages day-to-day workspace configuration and team matters; is not equivalent to the owner |
| Member | Uses the business features and Telegram accounts they have been granted access to |
The member action menu shows role changes, suspension, restoration, removal, and ownership transfer according to your permissions. Ordinary member actions cannot directly manage the owner or change your own role. The available menu and server validation are authoritative.
Suspending or removing a member revokes their workspace access. For unfinished tickets, the system clears assignees who are no longer eligible and notifies administrators. Administrators should review unassigned tickets.
Check the recipient before transferring ownership. The previous owner becomes an administrator after the transfer. Leaving a workspace requires a new invitation to rejoin; owners should resolve ownership before leaving.
Common questions
| Symptom | What to do |
|---|---|
| An invitation was created, but the person has not joined | An invitation is only a link; the recipient must sign in and accept it |
| A member can enter the workspace but cannot see messages | Check the View permission in the Telegram account's member grants |
| Member management buttons are missing | Check your role and workspace capabilities; not every member can manage the team |
| The page asks for password verification | Enter the current operator's TgSpark sign-in password, not the Telegram two-step verification password |
| Data changed or a version conflict is reported | Refresh the data and try again to avoid overwriting someone else's changes |
Implementation references: identity API and workspace settings.