# Accounts · Chromia Docs (concept)

> FT4 accounts can be registered with transfer open, transfer fee, or transfer subscription strategies, each offering flexible access options.

Source: https://docs.chromia.com/build/ft4/backend/accounts/

# Accounts

FT4 accounts can be registered with transfer open, transfer fee, or transfer subscription strategies, each offering
flexible access options. auth descriptors control account access, while account\_link manages relationships between
accounts for scenarios like staking and asset locking.

[Register FT4 accountsRegister FT4 accounts using strategies like transfer open, transfer fee, or transfer subscription. Admin operations allow authorized users to create accounts directly, while custom operations enable tailored registration with enhanced security measures.](https://docs.chromia.com/build/ft4/backend/accounts/overview/) [Transfer open strategyThe transfer open strategy requires users to transfer tokens to a non-existent account, which they must then claim
to activate it. This provides a middle ground between completely free account creation and paid strategies,
requiring token transfer but no fees.](https://docs.chromia.com/build/ft4/backend/accounts/open/) [Transfer fee strategyThe transfer fee strategy requires users to transfer a specific amount of tokens to a non-existent account, with
part of the transferred assets collected as a fee. This approach provides a clear and easy-to-follow process for
users who prefer straightforward access.](https://docs.chromia.com/build/ft4/backend/accounts/fixed/) [Transfer subscription strategyThe transfer subscription strategy requires users to pay regularly to access dapp functionality, helping generate a
steady income to sustain and grow the dapp. Users must periodically renew their subscription by paying the
subscription fee.](https://docs.chromia.com/build/ft4/backend/accounts/subscription/) [Use auth descriptors for accountsAccounts can have multiple auth descriptors, with one main descriptor controlling access. Descriptors can be
replaced and linked to the account with specific rules, while the main descriptor cannot be deleted.](https://docs.chromia.com/build/ft4/backend/accounts/accounts-and-auth-descriptors/)[Link FT4 accountsThe account\_link entity manages relationships between accounts, supporting scenarios such as staking, asset locking, and auctions. It enables flexible workflows with secure asset handling for both user-controlled and system-managed accounts.](https://docs.chromia.com/build/ft4/backend/accounts/account-linking/)

[View this page on docs.chromia.com](https://docs.chromia.com/build/ft4/backend/accounts/)Content mirrored from the live docs
