Team Members
In the app: Settings → Team
Needs the 'View Team' permission.
Everyone who has an account in your organization: who they are, which role they hold, which stores they can see and how many tickets they carry. From here you invite people, change their role and store access, deactivate them and hand over ownership.
Member list
The table lists every account in alphabetical order, including deactivated ones and people who have not accepted their invitation yet. Permanently deleted accounts are not listed. "Search team members..." filters the list by name or email address.
- "Member": name and email address. "(You)" marks your own row. An "Inactive" badge marks a deactivated account. The dot on the picture shows whether the person is online (green), away (yellow) or offline (grey); for someone who has not accepted yet it is yellow, and red once the invitation has expired.
- "Role": the role or roles the person holds. Purple is the Owner, blue a standard role, green a custom role. What a role allows is under Settings → Roles.
- "Status": "Online", "Away" or "Offline" for people who have set up their account; "Pending Invite" for someone who has not accepted yet; "Invite Expired" when the invitation link ran out before it was used.
- "Stores": "All stores", or the names of the stores the person is limited to. This column shows what is stored for the account, also for the Owner (see "Transfer Ownership").
- "Capacity": the stored workload counter against the person's limit, for example "3/10". The counter can differ from the actual number of assigned tickets and can stop increasing at the limit. The bar is green, turns yellow from 80% and red at the limit. This column is hidden when capacity limits are switched off under Settings → Organization, where the limits are also explained. Hiding only works for a viewer who also has the 'General Settings' permission; everyone else always sees the column.
- "Actions": the menu with everything you can do to that person. The menu uses your permissions to decide which actions to show. Some actions need an additional permission when you save; see "Deactivate and reactivate". If nothing applies, the button is greyed out.
You cannot change your own account from this list: your own menu is disabled with "Cannot modify your own account". Change your name and password under Settings → My Profile; your role and store access have to be changed by someone else.
If the list cannot be loaded, the page shows "Couldn't load the team." with "Try again". "No team members found" appears when a search matches nobody.
Invite Member
Needs the 'Invite Members' permission.
"Invite Member" opens the "Invite Team Member" dialog. The person gets an email with a link to set their own password. The link works for 7 days.
- "Email": the address to invite. It must not already belong to someone in your organization, deactivated accounts included.
- "Full Name": the person's name. They can change it later in their own profile.
- "Role": one role, required. Every role is offered except Owner; ownership can only be handed over with "Transfer Ownership".
- Store access: which stores the person will see. See "Store access" below. It has to be chosen before the invitation can be sent.
Above the buttons, a line sums up what you are about to send: "Inviting … as … with access to …". "Send Invitation" creates the account and queues its invitation email. If background dispatch fails, Squid tries sending directly. A successful queue request does not confirm delivery.
Limits on what you may hand out:
- You can only invite someone with a role whose permissions you all hold yourself.
- Inviting someone as Admin or Supervisor, or with any role that can manage or assign roles or deactivate people, needs the 'Manage Roles' permission.
- You cannot give access to stores you cannot see yourself.
After sending, the dialog shows "Invitation sent!". If it shows "User invited" instead, the account was created but dispatch or the immediate sending attempt failed. An email already queued can still be retried automatically; "Resend Invite" is available from the person's menu. The new person appears in the list with "Pending Invite", and their role and store access can already be changed.
The invitation limit is 10 requests per minute from the same IP address, shared by people using that address. Extra requests are refused with "Too many invites in a short time. Wait a minute and try again."
Store access
Needs the 'Assign Roles' permission.
Store access decides which stores a person sees. It is set on the invitation and can be changed later in "Edit Member". Changing it needs the 'Assign Roles' permission.
- "All stores": the person sees tickets, customers, reports and search for every store in the organization, including stores that are added later. This is what a member has unless it was narrowed.
- "Only selected stores": tick the stores the person may see; at least one. Everything else is hidden from them, not only filtered: tickets of other stores cannot be opened, and the inbox, customers, search, the dashboard and the reports only count the selected stores. The "Live Agents" report is the exception: it lists teammates, not tickets, and stays organization-wide. Stores added later are not included. The person can still read every automation rule and SLA policy, but can only create or edit ones that apply to their own stores.
If your own account is limited to certain stores, you can only hand out those stores. On an invitation "All stores" is then not offered. In "Edit Member" it is still shown, but saving it is refused with "Your own account is limited to selected stores, so you cannot give a member access to all stores."
The Owner's store access cannot be changed in "Edit Member": the dialog shows "The organization owner always has access to every brand." in place of the picker, and limiting the Owner to selected stores is refused. One catch: "Transfer Ownership" does not change the new Owner's store access. Someone who was limited to selected stores stays limited to them as Owner, and the picker is then locked, so set that person to "All stores" before you transfer.
Someone who invites without the 'Assign Roles' permission gets no picker. They tick a confirmation instead: the new person gets the same store access as the inviter ("Confirm access to all current and future stores.", or the inviter's own stores).
You cannot change your own store access.
Edit Member
Needs the 'Edit Members' permission.
"Edit Member" in a person's menu opens the "Edit Team Member" dialog.
- "Full Name": the person's name; it cannot be empty. The email address cannot be changed here; people change their own under Settings → My Profile.
- "Role": shown to people with the 'Assign Roles' permission. Pick one role; when you pick a different one, it replaces the role or roles the person had. Owner is not offered, and the Owner's own role cannot be changed here; that takes "Transfer Ownership". The new role may only add permissions that you hold yourself. At least one active person who can assign roles must remain in the organization, so the last such person cannot be moved to a lesser role.
- "Store access": shown to people with the 'Assign Roles' permission. See "Store access" above.
- "Max Capacity": the person's ticket limit. A whole number from 1 to 100; the default is 10. Nothing holds a person to the limit today: the limit is only checked when Squid itself picks a teammate for a ticket, which no part of Squid does at the moment, and assigning by hand, claiming, rules and "Auto-Assign on Reply" all go past it. Settings → Organization explains this. The workload counter is not a reliable count of every assigned ticket. It cannot be lower than the number of tickets the person holds right now. Because the dialog sends this value with every save, saving is refused for a person who already holds more tickets than their limit, even when you changed something else; raise the limit first. The field is hidden when capacity limits are switched off under Settings → Organization, for a viewer who also has the 'General Settings' permission.
- "Active (can access the system)": untick to deactivate the person, tick to reactivate them. The tick box is shown to everyone who can open the dialog, but changing it needs the 'Deactivate Members' permission; without it the save is refused. See "Deactivate and reactivate".
"Save Changes" saves in three steps: first name, capacity and the active tick, then the role if you picked a different one, then store access if you changed it. If a later step is refused, the earlier steps stay saved. A new role or store access applies from the person's next action in Squid; they may have to reload the page before menus follow.
Resend Invite
Needs the 'Invite Members' permission.
"Resend Invite" creates a new invitation link that works for 7 days and queues another email. The page can show "Invite resent" even when dispatch failed and the email is waiting for an automatic retry. Resending is limited to 5 requests per minute from the same IP address. Use it for "Pending Invite" and "Invite Expired". The menu shows it for every other active person, whatever their status. For someone who has already set up their account it answers "This user has already set up their account"; that person should use the forgotten-password link on the sign-in page instead. For someone who was never invited by email, such as the person who created the organization, it answers "This user was not invited via email".
Deactivate and reactivate
Needs the 'Deactivate Members' permission.
"Deactivate" asks for confirmation in the "Deactivate User" dialog. The person loses access at once: they are signed out everywhere and AI apps they connected are disconnected. The account stays in the list with an "Inactive" badge and can be reactivated later. Unticking "Active (can access the system)" in "Edit Member" does the same.
Deactivating does not touch the person's tickets. Tickets assigned to them stay assigned to them, so reassign those yourself.
"Reactivate" in the menu of an inactive person gives access back with the same role and store access as before. AI apps that were disconnected stay disconnected; the person connects them again.
You cannot deactivate yourself, and you cannot deactivate the last active person who can assign roles.
The server asks for the 'Deactivate Members' permission, and for "Reactivate" also for 'Edit Members'. The menu shows "Deactivate", "Reactivate" and "Permanently Delete" only to people who hold 'Assign Roles', so from the menu you need both. Someone with 'Edit Members' and 'Deactivate Members' but without 'Assign Roles' uses the tick box in "Edit Member" instead.
Permanently Delete
Needs the 'Deactivate Members' permission.
"Permanently Delete" is only offered for an inactive account: deactivate first. After you confirm in the "Permanently Delete User" dialog:
- the person's name, email address and picture are erased from the account. Wherever Squid looks the account up, such as in ticket history, the person is shown as "Deleted User". Audit log entries written earlier keep what they recorded: the entry for the invitation keeps the name and email address, the entry for the deactivation the email address;
- tickets that were still assigned to them become unassigned;
- the account can never sign in again, and the row disappears from the list.
This cannot be undone. Replies and notes the person wrote stay in the tickets.
Transfer Ownership
Only the Owner sees "Transfer Ownership", in the menu of another active member (not the AI agent). Ownership belongs to one person at a time; the role cannot be given with an invitation or in "Edit Member".
The "Transfer Ownership" dialog names the person who will become Owner. Type TRANSFER_OWNERSHIP in the field to enable the button. After the transfer that person is the Owner, next to the role they already had, and you become an Admin: the Admin role replaces every role you held. Store access does not change for either of you (see "Store access"). You cannot take it back yourself; only the new Owner can transfer it again.
As Owner, the (i) button next to the page title reminds you of this. The option only appears once someone else is on the list.
The AI agent
The AI agent has its own row, marked "System account". In place of an email address the row says "Answers customers on your behalf. No mailbox, no sign-in." Its status reads "Set in AI settings", because whether the AI answers is decided per store in the AI section, not here.
Its menu has "Rename", for people with the 'Edit Members' permission, and "AI settings", which opens the AI settings page. It does not open the "Advanced" section automatically. "Rename" changes the name of the AI agent's account as it is shown inside Squid, for example in this list. The dialog says this is the name customers see on replies the AI sends, but that is not what happens: emails and chat replies from the AI are signed with the agent name set for each store in the AI section, or the store's name when none is set.
The AI agent cannot be deactivated, deleted, made Owner, sent an invitation or limited to certain stores. To stop the AI from answering, turn it off for a store in the AI section.