Roles & permissions
TelePong’s access model is granular by design: every capability — reading chats, sending content, seeing finance, changing settings — is a separate permission, grouped into roles.
Built-in roles
Four presets cover most agencies:
| Role | Chats | Vault | Campaigns | Finance | Settings |
|---|---|---|---|---|---|
| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |
| Manager | ✓ | ✓ | ✓ | view | partial |
| Chatter | assigned models | send only | — | — | — |
| Finance | — | — | — | ✓ | — |
Built-in roles are live: when TelePong ships a new feature, the presets gain sensible defaults automatically.
Custom roles
Create custom roles when a preset doesn’t fit — for example, a «Senior chatter» who can also manage the Vault, or a «Traffic manager» who only sees tracked links and campaign stats. Custom roles keep exactly the permissions you set; new features arrive disabled until you enable them.
Model scoping
Permissions answer what a person can do; model assignment answers where. Every non-owner is assigned specific models, and everything — dialogs, Vault, analytics — scopes to that assignment.
Folder-level access
Within a model, folders can be restricted further — both chat folders and Vault folders.
What chatters can never do
Regardless of role configuration, some things stay owner-controlled:
- adding or changing payout requisites,
- seeing masked fan contact details,
- erasing history — deletions and edits stay in the owner’s log.