> ## Documentation Index > Fetch the complete documentation index at: https://www.help.creatora.io/llms.txt > Use this file to discover all available pages before exploring further. # Access, authority, and delegated work > Understand Administrator access and agree the scope of work delegated to someone else. Every Administrator on a Creatora platform has the same product permissions. There is no separate owner, super-administrator, or technician role. A Student has a different role for learning and account use. ## Agree who can approve the task Administrator access lets someone use the administration features on that platform. For decisions involving business terms, payments, personal data, domains, or an external provider, agree with the responsible person who may approve the change. Access to an account or possession of a PIN, token, or API key is not approval. For example, an Administrator can reach checkout settings in Creatora, while the person responsible for the Stripe account may need to approve a payment-method change. A technician with access to a domain provider does not gain an Administrator role in Creatora. ## Delegate a specific job Before a technician starts, agree on the platform and external accounts involved, the change to make, the data they may access, who approves each part, and when access should end. Give them only the access the job requires. Afterward, check the specific result in Creatora and any external service involved. Keep PINs, tokens, and API credentials private. If a payment, access change, deletion, or data transfer has an unclear result, check what happened before approving another attempt.