Treat inventory as an operating record
An account inventory explains where each account came from, who currently controls it, who operates it, and which recorded costs belong to it. It should cover both unassigned accounts and accounts already allocated to the team.
Without that record, departures and role changes become a search through private messages. Even a small inventory is useful when more than one person handles access. The goal is continuity and traceability, not a larger collection of credentials.
Limit the process to accounts the organization legitimately controls
Establish account ownership and authorized use before adding an account to inventory. Check the applicable platform requirements for account creation, access, and any transfer. This guide describes internal recordkeeping, not an account sourcing service or a way around platform rules.
Keep recovery ownership clear. The organization should understand who controls the associated recovery channels and how access is revoked during a handoff. A software record alone cannot establish ownership or guarantee that an account is transferable.
Record identity, ownership, source, and cost
Useful fields include handle, stable ID, account type, market, group, source, recorded acquisition or setup cost, start date, owner, and status. Restricted access records may include login and recovery details where the organization is authorized to hold them.
Prevent duplicate records for the same identity. Correct mistakes with a visible history and mark invalid records rather than casually deleting them. Cost and start date are particularly difficult to reconstruct later, so capture them while supporting records are available.
Keep access material encrypted and narrowly visible
Passwords, two-factor secrets, and mailbox credentials should not appear in the general operations sheet. Use encrypted storage, limit viewing to people who need access, and retain a record of who viewed it and when.
A handoff should have one authoritative access record. Avoid leaving uncontrolled copies in inventory, messages, and personal files. Star Captain's allocation workflow transfers the relevant access record out of the unassigned inventory view; confirm the recipient and their role before allocating it.
Use request, approval, and allocation as separate steps
An employee request should state quantity, type, market, and business reason. An authorized manager reviews it, with a reason for rejection where applicable. The inventory operator then allocates specific accounts and records what was issued.
Link an allocation to an approved request when one exists. Otherwise an employee can receive an account while their request still appears open. The receiving employee should verify access and complete the appropriate authorization flow before the account is treated as ready for work.
Make departures and role changes a real handoff
List the departing owner's accounts, status, open drafts, active tasks, and access changes. Have the receiving owner verify the list. Record the new owner and effective date, and check which ownership rule the reporting system uses for historical performance.
Revoke the departing employee's access while retaining necessary history. Do not assume that changing today's owner preserves historical attribution by date. Review the final pay period and unresolved business separately so neither an account nor an obligation disappears from the process.
Record costs once, then connect them to reporting
The inventory cost should connect to the operational account and the configured cost treatment. Do not enter the same account expense again in a manual ledger if the linked record already supplies it.
Paused or restricted accounts still have historical costs and results. Retain enough history to review recovery and loss. The profit guide explains payback, and the Showcase check guide explains how to distinguish a verified issue from a data gap.
Use Star Captain's account inventory workflow
Star Captain places inventory and allocation in the Business center for authorized staff. The workflow records requests, approvals, assignments, and access views. Employees receive allocated accounts in their own work area and authorize them for supported data access.
Recorded inventory cost can link to the corresponding operational account, avoiding a second manual entry. Inventory and allocation are described in Starship and Galaxy; check pricing and the actual role setup. Start with a small handoff and verify the receiving employee's view before expanding.
Frequently asked questions
What should an account inventory record contain?
Identity, market, type, ownership, source, dates, status, and supported cost records. Keep sensitive login and recovery material in a separate restricted workflow.
How should a team store account passwords?
Use encrypted storage, need-based access, and view records. Avoid shared spreadsheets and group messages, and establish one authoritative record for each handoff.
What is a useful account request process?
Request the type, quantity, market, and reason; approve or reject it; allocate specific accounts; then have the recipient confirm access and authorization.
What happens when an employee leaves?
Verify the account and task checklist, assign a receiving owner, record the effective date, update access, and retain history. Check reporting attribution and the final pay period separately.
Should inventory cost also be entered as a manual expense?
Not if the linked account record already contributes that cost. Reconcile the source before adding an expense to avoid counting the same amount twice.
Which plans include inventory and allocation?
The documented comparison includes this workflow in Starship and Galaxy. Verify current pricing and permissions; employees request or receive accounts rather than managing unrestricted inventory.
Related guides
Put it into practice: Explore TikTok accounts →
