EYT Experiences · Operator resources
Partner Permissions & Commercial Control

Clarify Company authority, Creator assignments, Guest privacy and commercial boundaries in the EYT platform model.
- Company authority
- Assigned role
- Necessary information
- Review
Permissions should follow a legitimate task
Clarify Company authority, Creator assignments, Guest privacy and commercial boundaries in the EYT platform model.
Access to a Party should reflect what someone needs to do. A Guest needs their experience information, a Host needs assigned coordination context and the company needs operational oversight. A role name alone should not imply permission to change prices or disclose unrelated Guest information.
Map decisions to tasks
Begin with practical actions: view a Guest detail, update arrival information, recommend an applicant, approve a service or change a commercial term. Ask which role needs each action and for what purpose. A broad label such as Host or Partner is not a sufficient permission specification. The company should review the actual assignment and the operational context before granting access to sensitive or commercially consequential information.
Review the end of an assignment
Temporary coordination needs should not silently become permanent access. Ask how the proposed workflow handles a Host who no longer supports a Party or a staff member whose responsibilities change. Check what Guests can see about their own experience and what remains internal. These are validation questions for a controlled Partner workflow; a public page cannot substitute for inspecting the actual permission behavior of a particular enabled capability.
Illustrative operating scenario
The following is a hypothetical workflow example, not an EYT customer case study. A temporary Host supports arrival for one group. The company defines that assignment without giving the Host unrestricted visibility into other clients or permission to approve refunds.
Examine commercially consequential actions
Changing a price, approving a supplier and recording a Guest arrival carry different consequences. Review permissions at the action level and check the evidence required for a decision. Someone able to update operational information should not automatically be assumed to have authority over provider funds or cancellation terms.
Test a boundary with real roles
Ask how the proposed workflow behaves when an assigned Host tries to view an unrelated Party, or when a Guest follows a link to information outside their experience. These are concrete permission questions for the enabled workflow. Marketing descriptions of role separation should be validated against actual behavior before expanding access.
Commercial boundary
For this workflow, the Company retains clients, suppliers, availability, pricing, approval, relevant payment collection and fulfillment. Its terms govern cancellation and refunds. Keep the tools that already work for you; no automatic integration or replacement is implied.
Operating framework
| Checkpoint | Question to resolve | Responsible context |
|---|---|---|
| Access | Which information is necessary for this task? | Reviewed role assignment |
| Authority | Can this person approve a commercial change? | Company permission |
| Offboarding | What access ends with the assignment? | Company access review |
Questions operators ask
Does this replace our existing operating systems?
No automatic replacement or integration is implied. Confirm the proposed workflow alongside the booking, CRM, payment and supplier systems that already work for your company.
Is every described capability available to every Partner?
No. Current availability and permissions depend on the controlled Partner workflow. Platform-model and future-direction descriptions should be confirmed during onboarding.
Who retains commercial authority?
The responsible company retains pricing, supplier approval, fulfillment and the relevant payment and cancellation decisions under its own terms.