TOKEN SUPPLY / OPERATIONS
Workspace overview
Only handle the accounts and tasks within the assigned scope, and follow up the data and operation results one by one.
Staff access has not been verifiedProtected data not yet obtainedSnapshot time:not read yet
Start account intake
Use separate workflows for complete channel delivery, staged vendor collection and personal owner authorization.
Prioritize follow-up
Sort by loaded recordsReading staff permissionsAfter accessing the real snapshot, the account, task and source time are displayed.
Processing order of this class
- 01First check the missing information and the original account file.
- 02Check the task receipt and the platform collection time to avoid repeated account access.
- 03Write down processing notes, resume original tasks and hand over unfinished items.
Fund operations, official quota reset and cloud procurement are not performed in this workbench.
Business entrance
Three types of customers, handled separatelyChannel account
Check fields according to complete delivery requirements and follow up platform operation data.
Viewing scope is determined by staff assignmentsAccount vendor
It is allowed to complete in stages, paying attention to the integrity of the data and the results of accessing the account.
Viewing scope is determined by staff assignmentsPersonal authorization account
Check my authorization, unique operating qualification and true income receipt.
Viewing scope is determined by staff assignmentsOperator guide
First look at the accounts you are responsible for and the missing items, and then check the original tasks and platform reports. Write the processing instructions in the notes, and restore the original request if it fails; do not create the same account again or redeem the authorization again.
Before intake, select an assigned owner. Channels require complete fields; vendors may complete records later; individuals authorize personally. Preview batches, then confirm create, update, or skip per row.
The page only refreshes and saves snapshots every 30 seconds; if the query fails, the original time is retained and writing is suspended, and private data is cleared when permissions expire.