Request another team or account

Self-service team creation is not generally enabled in production. The Create team menu or route may exist, but a normal account can receive a notice that creation is disabled. This does not prevent switching between existing teams or accepting an invitation.

Decide what you need#

• The agency already exists: you do not need a new team. Register and verify your account with the correct email and request an invitation from its administrator.
• A team you previously used is missing: check the active team, invitation, email address, and whether your access was disabled. Follow Understand teams and switch agencies safely.
• You are contracting a separate commercial account: agree the onboarding with Holidario before loading properties, users, or data.
• You only need to separate functions or properties: do not create another account by default. First confirm whether roles, resource authorizations, or another structure inside the existing team should handle it.

A second team has its own subscription, users, permissions, properties, and operating context. It is not a folder inside the current team.

Information for requesting onboarding#

The owner or administrator should prepare:

• commercial name and account owner;
• email of the person who will administer the team;
• expected plan and approximate property volume;
• whether the rentals already belong to another Holidario team;
• target date and reason for the separation;
• which users need to belong to both teams.

Do not send passwords, guest documents, certificates, or channel keys to request onboarding.

Avoid duplicates#

Do not continue if the name or properties already appear in another team. Confirm which account will retain the data and who authorizes any transition. Creating a duplicate does not move reservations, history, connections, billing, or permissions.

The process is complete when Holidario confirms the correct commercial team, its administrator signs in with their own account, and they can clearly identify the active context. Until then, do not load the same portfolio into two teams as a test.