Manage Developer access

Developer access lets a teammate use limited technical integration tools without giving them customer-data, Team or billing access from that preset.

How it works

Developer access is added alongside a person's workspace role. An Accountant, Operations or Support member keeps their other permissions. Only a workspace owner or admin can add or remove it.

Technical controls live in Qcom Developer Platform. Ordinary supported applications stay in Settings → Integrations and do not require this preset. An eligible plan or an existing developer entitlement is still required; assigning access does not change billing or the plan.

The initial tools support limited verification API credentials and synthetic test webhooks. Additional customer-data scopes and outbound customer-data webhooks remain blocked until a supported independent approval path is available. A developer cannot approve their own sensitive request, even if they are also an admin. A sole owner cannot bypass independent approval.

Give someone access

1. Open Settings → Team.
2. For a dedicated developer, choose Add Member, enter their email, choose No operational access, enable Developer access, then send the invitation.
3. For an existing employee, turn on Developer access beside their name. Their other roles and permissions stay unchanged; no second invitation is sent.
4. For a pending invitation, change its Developer access switch before the person accepts. The invitation link and remaining access stay the same.

On mobile, the switches are in the invitation form, member actions and pending invitation actions. Save member changes before closing the member sheet.

The person joins with their normal Qcom account. If the person who authorised a pending developer invitation can no longer grant that access, a workspace owner must issue or review the invitation again.

Remove access safely

Turn off the person's Developer access switch. This removes only that preset. Permissions independently granted by another role or custom setting remain. Business-owned integration credentials are not automatically revoked.

Use the credential owner's revoke or disconnect action separately when a business integration must stop. Removing a person from the workspace is a different action.

When it doesn't work

• You turned it off: turn it on again only if the person still needs it.
• The workspace isn't eligible: ask the owner to check its existing plan or developer entitlement. Repeated sign-in attempts cannot change eligibility.
• Sensitive scope approval isn't supported: those permissions stay blocked, rather than allowing self-approval or an automatic Platform Admin bypass.
• The access changed while you were saving: refresh and review the current access before trying again.
• Qcom couldn't save the change: try again; if it continues, ask your workspace owner for help. Do not remove and reinvite an existing employee as a workaround.

Related

• Manage your team and roles