End Users
Manage End Users, AI credit allocation, and consumption history.
End Users are users from your own product who open and use the editor.
They are not AuroraSendCloud Accounts. They do not log in to the Platform Console. Your backend maps them into an Application through the API.
How End Users are created
End Users are created or refreshed when your backend calls:
POST /access/tokenExample request body:
{
"id": "user_12345",
"name": "Jane Doe",
"email": "[email protected]"
}The id is your external identifier for the End User. It must be unique within the Application.
If the id does not exist yet, ASC Editor Plugin creates a new End User mapping. If it already exists, the token is refreshed for that End User.
End Users table
The End Users table shows mapped users in the current Application.
| Column | Description |
|---|---|
| ID | Your external End User identifier. |
| Name | Display name, if provided. |
| Email address, if provided. | |
| AI Credits Assigned | Total AI credits assigned to the End User. |
| AI Credits Used | AI credits consumed by the End User. |
| AI Credits Remaining | AI credits still available to the End User. |
| Status | Current access or usage status. |
Credit allocation
Credits belong to an Application first. You can allocate credits from the Application credit pool to individual End Users.
Use credit allocation to:
- Limit AI usage by End User.
- Support resale or customer-specific plans.
- Prevent one End User from consuming the full Application pool.
- Track usage by external user.
Allocate credits
- Select one or more End Users.
- Click Allocate Credits.
- Enter the credit amount.
- Set an expiry date, if required.
- Confirm the allocation.
Each allocation creates a credit record with its own amount and expiry.
Credit consumption
When an End User uses a credit-based feature, credits are deducted from that End User's available allocation.
Credit-based features can include:
- AI email generation
- AI rewrite
- Inbox Preview
The exact credit cost depends on your plan and product configuration.
When credits run out
If an End User has no available credits for a feature:
- The editor can still be opened if the End User has access.
- Manual editing can continue.
- Credit-based features may be hidden or disabled.
- You can allocate more credits from the Application pool.
Usage history
Use the End User detail view to inspect credit allocation and consumption history.
History can include:
| Field | Description |
|---|---|
| Time | When the allocation or consumption happened. |
| Feature | Feature that consumed credits. |
| Credits | Number of credits allocated or consumed. |
| Remaining | Balance after the event. |
| Expiry | Expiry date of the allocated credits. |
Notes
- End Users exist only within the Application where they are mapped.
- The same external user ID can be used in different Applications without sharing usage records.
- End User access starts from your backend. End Users do not sign in to AuroraSendCloud.
- Keep your external user IDs stable to preserve usage history.
Updated 6 days ago