Start with the right owner
Heads and managers can share personal invitation links. New affiliate applications retain the association through the approval process.
PEOPLE & PERMISSIONS
A bigger team.
A clearer structure.
Organise heads, managers and affiliates. Give each person a useful workspace with access appropriate to their responsibilities.
ROLE EXPLORERINTERACTIVE EXAMPLE
Programme owner
Head of Affiliates
Manager → affiliates
Direct affiliates
Illustrative default scope. Additional permissions are configurable and must be reviewed.
THE DETAILS
From invitation to daily work.
See the relationships
Team organograms connect people and the financial indicators available to the viewer for the selected period.
Configure permissions
The super-admin can grant additional functions by role. Wider administrative access can expose organisation-level information, so review the scope carefully.
THE DETAILS
Understand the affiliate’s experience.
Enter as a team member.
The super-admin can inspect other active users in the organisation. A Head of Affiliates is limited to the supported subordinate team scope.
The temporary session identifies the member being viewed, records the action and keeps restrictions on sensitive operations. It is a support workflow, not a way to bypass permissions.
An affiliate workspace that stays focused.
- Assigned offers and agreed commissions
- Links, sources and external click IDs
- Own performance and reported player activity
- Payment accounts, requests and notifications
- Role-specific help and support tickets
GOOD QUESTIONS
A little more clarity.
Does an invitation automatically approve an affiliate?
No. The invitation creates the association, while the usual application approval still applies. It does not automatically assign offers or commission agreements.
Can an affiliate see the programme’s internal margins?
The affiliate view is restricted to its own authorised data and commissions. Internal revenue and costs belong to restricted administrative views.
YOUR NEXT CHAPTER