Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Connect Atlassian managed-account product access. Read managed-account access without implying coverage of every external or unmanaged user. Current availability: Read adapter implemented; company authorization and successful live sync required.

Before you start. An authorized company administrator with Vendor licenses management permission and an approved provider data-use scope. The company’s protected integration vault. Use a dedicated provider application; never put credentials in a KB, video, chat or source file.

Step 1. In Atlassian Administration, create a dedicated organization API key authorized for read:accounts:admin and record the correct organization ID.

Step 2. Enter the Atlassian organization ID and protected API key in its provider form. This vendor ID is separate from the LastStop Connect company ID.

Step 3. Save the encrypted connection in Companies > company > Vendor licenses. Choose Sync now in production after provider authorization. Dev and QA isolate external operations. Review the recorded sync result and compare the snapshot with the provider console.

Step 4. Review each managed account’s returned product access and status. Product records distinguish sites, so Jira access on two sites remains separate.

Step 5. Reconcile against the managed-account view in Atlassian. This GET endpoint does not cover every unmanaged or external user, purchased-seat total, project role or resource permission.

Now verify the result. A pagination link for a different organization is rejected. Capacity stays unknown when only account access is returned. A successful company sync is required before describing the connection as healthy; an available adapter alone is not a connected account. Check a second company and a view-only account: neither can change this company’s credentials or lifecycle state. Pause, Resume and Trash affect only the local connection. Resume waits for a separate Sync action; no vendor user or license is modified.

If you get stuck. 401 or 403: check credential expiry, the selected provider organization and the exact required permissions. Do not grant broad write access merely to bypass a failed read. A failed or incomplete provider response preserves the last complete snapshot. Review the error, correct the connection and explicitly retry. On a 429 rate-limit response, wait for the provider’s retry window before another manual sync. Large inventories can require a separately designed scheduled export; the current bounded sync does not commit partial results.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.