An employee invitation connects a verified Aplauso identity to a defined business scope. The server enforces the organization, location, department, service point, role, recipient binding, expiry, and use limit. Creating or accepting an invitation does not itself prove access beyond that scope, payment availability, Wallet eligibility, or payout readiness.
Create a scoped invitation
You need the relevant people-invitation capability for the intended business scope. In the available Business team controls, choose the role and location, and add a department or service point when it applies. Use only a recipient, expiry, and use limit offered by the current form. Share the resulting code or link through an approved channel with the intended person.
Do not promise a bulk import, a fixed dashboard route, a particular role, or an immediate invitation delivery outcome from this guide. An email-bound invitation can only be accepted by the matching verified identity.
Help the employee accept access
The recipient verifies a phone number or email address they control through the current passwordless onboarding flow, then enters the invitation code when that option is shown. After completion, confirm that the expected business access is visible. An invalid, expired, revoked, exhausted, already-used, or email-mismatched invitation can fail without creating the intended assignment.
Never ask an employee to send a verification code, password, card data, bank data, or token. If acceptance fails, the authorized inviter should review the invitation's scope and status, then create a replacement only when appropriate.
Confirm and maintain assignments
Review the team record through your authorized business controls. Role and assignment changes remain limited by capability and hierarchy; a title alone is not proof of organization-wide access. Manage existing access through the available team and role-assignment workflow instead of treating a used invitation as ongoing access control.
An employee profile, guest link, Reward Code, or Wallet screen does not confirm that live payments or payouts are available. Use the status displayed in the authorized product experience for those decisions.
Get help safely
For an access issue, provide the authorized business scope, displayed role or assignment, approximate time, and a non-sensitive error or reference. Do not include an invitation code, verification code, payment information, bank information, password, or token in a support request.