The following discussion from !5791 should be addressed: - [ ] @sdejonge started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/5791#note_3193102785): (+3 comments) > **thought:** I wonder if we can leverage the same `FIGMA_TOKEN` for both since they are pretty similar, wdyt? > > ```suggestion:-41+0 > # To get your Figma API token (FIGMA_TOKEN): > # 1. In Figma homepage, click profile picture and select "Settings" > # 2. Go to "Security" tab > # 3. In "Personal access tokens" section press "Generate new token" > # 4. Give your token a descriptive name and select scopes: > # 4.1 file_content:read - Figma design token sync / Figma code connect > # 4.2 file_variables:read - Figma design token sync > # 4.3 file_variables:write - Figma design token sync > # 4.4 file_code_connect:write - Figma code connect > # 5. Copy the generated token (starts with "figd_") > FIGMA_TOKEN="figd_ABC123" > > # To get the Figma file ID (FIGMA_FILE_ID): > # This should point to the design token library file > # 1. Open the design token library Figma file > # 2. Right-click on file name and select "Copy link" > # 3. Copy the FILE_ID from URL https://www.figma.com/design/{FILE_ID}/ > # > # For a specific branch: > # 1. Switch to your desired branch in Figma > # 2. Copy the BRANCH_ID from URL: https://www.figma.com/design/{FILE_ID}/branch/{BRANCH_ID} > FIGMA_FILE_ID="ABC123" > ``` TLDR * Should we reuse the same PAT for different tasks? * How might we rename the syncing env variable names to be clearer * I don't think we can change the name of the code connect one as that is determined by code connect cli