EDS learning

Hi ​@sravanthi_B  ,

Please open https://admin.hlx.page/auth/adobe and sign in using the credentials of a user who has admin access.

Once the page loads successfully, open your browser's Developer Tools, navigate to Application/Storage → Cookies, and copy the value of the auth_token cookie.

By default, the user who installed the AEM Code Sync GitHub app is granted admin access, so you can use that account to retrieve the token.

HI ​@sravanthi_B ,

You can verify whether you have admin access or not using the AEM Tools https://tools.aem.live/tools/user-admin/index.html, If you don't have access, ask the repository owner or an administrator to grant it.
Second option is to get started following AEM best practices is to create your repository using the boilerplate GitHub repository as a template.
You can find more details here:
https://www.aem.live/developer/ue-tutorial

-Tarun

Hi ​@sravanthi_B 

Yes, you can learn the core EDS development workflow without using your organization's API keys. You can start with the official EDS Developer Tutorial, create your own GitHub repository from the boilerplate, and use Document Authoring (da.live) as the content source. This gives you a safe personal sandbox for learning EDS development.

However, if you specifically want to set up a repoless/config-service project or use AEM as the content source with Universal Editor, you will need a provisioned EDS organization/site and the appropriate admin permissions. In that case, ask the repository or organization owner to create a sandbox and grant access to your own user account.

I would not recommend copying or requesting someone else's auth_token cookie. It is a sensitive credential and must not be shared or stored in chat, screenshots, or source control. If you already have authorized access and only need a one-time API test, follow the documented authenticated Sidekick/Admin Service workflow, but keep the token private.

The User Admin tool can be used to verify or manage roles after access has been granted; it cannot provide access by itself.