Inputs
Subaccounts, users, permissions, extensions, enabled services, quotas and visual configuration.
Solution
Agencies and resellers
Manage customers and subaccounts centrally while retaining external control of pricing and billing.
Overview
Manage customers and subaccounts centrally while retaining external control of pricing and billing.
Who it is for
A solution designed for a specific operating context
Agencies and resellers managing multiple client accounts while keeping their own commercial relationship.
What changes when the process is connected
- Clients and resources mixed in one operating account.
- Manual and inconsistent setup when adding accounts.
- No consolidated view of quotas and usage.
Solution architecture
Connected inputs, capabilities and outcomes
Outcomes
Isolated client spaces, inherited settings, embedded Cloud and consolidated usage.
Capability map
| Features | Apification service | Expected outcome |
|---|---|---|
| Master account and subaccountsManage multiple customer accounts from a reseller-owned operational structure. | Apification for resellers | Group customer subaccounts under a master account and control services, permissions, quotas and consolidated usage. |
| Per-customer permissionsControl available services, extensions, roles and account defaults for each client. | Reseller integration | Embed Apification through Cloud iframe, API, inherited configuration and visual themes. |
| Storage and usage quotasAssign limits to subaccounts and review consolidated consumption from the master account. | Apification Cloud | Manage files, services and digital projects in an organized, versioned workspace designed for sharing. |
| Embedded customer CloudExpose Apification inside an external customer portal through signed iframe access and effective themes. | Plans and usage | Combine storage, services and credits for users, businesses, partners and resellers. |
Additional capabilities
Features that complete the solution
Automated account provisioning
Create users, subaccounts and initial configuration through the API.
Centralized production and delivery
Produce, version and share customer assets while keeping every project separated.
Independent commercial management
Keep contracts, final pricing and customer invoicing under the agency or reseller’s external control.
Complete scenarios
How it works in a practical case
Complete a process with fewer tools.
- Starting situation
- Clients and resources mixed in one operating account.
- Configuration and process
- Control available services, extensions, roles and account defaults for each client.
- Outcome
- Isolated client spaces, inherited settings, embedded Cloud and consolidated usage.
Coordinate people, resources and deliverables.
- Starting situation
- Manual and inconsistent setup when adding accounts.
- Configuration and process
- Assign limits to subaccounts and review consolidated consumption from the master account.
- Outcome
- Isolated client spaces, inherited settings, embedded Cloud and consolidated usage.
Improve operations using real activity data.
- Starting situation
- No consolidated view of quotas and usage.
- Configuration and process
- Expose Apification inside an external customer portal through signed iframe access and effective themes.
- Outcome
- Isolated client spaces, inherited settings, embedded Cloud and consolidated usage.
Requirements and limits
- Multi-client management requires a reseller account and separate subaccounts.
- Client contracts, final prices and invoices are managed outside Apification.
- Embedded integration requires defined domains, permissions, theme and operating responsibilities.
Security and privacy
- Each subaccount keeps independent users, resources, configuration and quotas.
- Users, groups, roles and visibility control who can view or change each item.
- Resources remain private until they are explicitly shared or published.
Integrations
- Cloud can be embedded in another portal through a signed iframe and effective theme.
- The API creates and queries resources; webhooks report changes and outcomes.
- Google Drive, OneDrive and Dropbox can supply source files.
Usage and planning
- Subaccount usage is consolidated under the reseller account.
- Originals, projects, versions and outcomes use the account storage quota.
When it fits
Check whether this solution matches your needs
When it fits
- You manage several clients from a central structure.
- Cloud must be embedded in your portal while billing stays external.
- Each subaccount needs different limits and services.
When another approach is needed
- You expect Apification to invoice every end client automatically.
- You do not need separate accounts, permissions or usage.
Frequently asked questions
Questions about Agencies and resellers
Yes. Cloud organisation, folders, groups, permissions, and separate services help maintain clear ownership and access.
Yes. Editable projects can stay private while exported files or published services are shared with clients.
Yes. Versions, studios, and File Transformer make it possible to derive channel-specific formats without replacing the source.