Business team controls show only the people, invitations, role choices, and assignments available to your signed-in scope. A management title or a visible page does not grant universal access to people, properties, departments, outlets, personal Wallets, financial details, or employment records. The server enforces the applicable role, capability, assignment, and organization rules for every action.
Create an invitation only when authorized
Creating an employee invitation requires the people.invite capability in the relevant Business scope. Use the current invitation form to select only the role and assignments it makes available. The server, rather than the person sharing a code, enforces organization, location, department, service point, role, expiry, recipient binding, and use limits when applicable.
Share an invitation only with its intended recipient through an approved channel. An invite link, code, draft message, or created record does not itself create an account, prove identity, grant access, or confirm activation. The recipient must complete the current identity and acceptance flow. Do not send verification codes, passwords, payment details, bank information, or private employee data.
Review assignments and changes carefully
Use the visible team record and confirmation flow to review a current assignment or available management action. Do not promise a fixed role list, hierarchy level, immediate activation, deactivation, removal effect, role-change timing, notification, data retention, performance metric, or access result. A change is authoritative only when the current server-enforced product state reflects it.
Personal earning, Wallet, payout, bank, identity, and private guest information remain separately protected. Team management does not authorize viewing or changing those records unless a distinct current workflow and permission grants it.
Escalate an access issue safely
For an invitation, role, or assignment question, provide the authorized Business scope, visible action or error, approximate time, and non-sensitive reference. Support can investigate the recorded state but cannot bypass organization authorization or expose another person’s private data.