Org
Org covers your organization’s own settings, plan usage and billing details. It exists so an integration can read how the account is configured and how much of its plan is consumed. See Settings Overview in the Help Center.Users
Users are the people on your team who sign in to ConveYour — distinct from contacts, who are the people you manage. They come as admins, who reach the whole account, and guests, who are limited to the contacts and conversations assigned to them; that difference changes what the API returns. They exist so access, assignment and audit trails point at a real person on your side. See Team Admins, Guests, and Adding New Users in the Help Center.Roles
Roles are named permission sets assigned to users, with built-in system roles alongside any your org defines. They exist so access is granted by job rather than person, and stays consistent as people change. See What are Roles? in the Help Center.Teams
Teams partition contacts and resources, and decide what any given request can see. They exist so one account can hold separate groups of people without them seeing each other’s data — which is why team scoping changes the results of almost every endpoint. See Teams Introduction in the Help Center.Compliance
Compliance checks whether your contacts have completed what your organization requires — lessons matched by tag, and form submissions matched by collection and status — then reports the outcome. You configure what counts (which tags, which submission statuses, how far back to look) along with an optional callback URL, and the check runs across your contacts. It exists so you can verify that a whole population meets a requirement rather than inspecting records one at a time. Configuration is org-wide and admin-only.Webhooks
A webhook posts to a URL you own when something happens in ConveYour. Each is registered against a record type and an event that type declares —contact.updated on a contact, or contact.joined on a campaign. The API is read-only here: you can list your registered webhooks and manage their credentials, but webhooks themselves are created in the app, not through these endpoints. This is also distinct from the outbound webhook step inside a campaign, which posts contact data as a workflow runs and can write fields back from its response — see Webhook Response Operations. They exist so your systems can react as things happen instead of polling for changes. See Webhooks in the Help Center.