PATs Created While Using Organization Workspace Are Still Limited to Free-Tier Credits

Hey ​@MattK_Censys, I believe there may be an issue with how Personal Access Tokens (PATs) are associated with Organization accounts.

Environment

• I have been granted 60,000 credits through an Organization plan.

• I can successfully switch between my Free workspace and the Organization workspace in the Censys web UI.

Issue

When I create a Personal Access Token (PAT) while using the Organization workspace, the token appears to be associated with my Free account instead of the Organization account.

As a result:

• API requests appear to use the Free-tier credit allocation (100 credits).

• Organization-level credits (60,000 credits) are not available through the PAT.

• Features that require Organization-level access cannot be used via the generated token.

Steps to Reproduce

1. Switch to the Organization workspace in the Censys web UI.

2. Navigate to the Personal Access Token creation page.

3. Create a new PAT.

4. Use the PAT for API requests.

5. Observe that usage appears to be tied to the Free-tier credit allocation rather than the Organization credits.

Expected Behavior

PATs created while operating within an Organization workspace should be associated with the Organization account and have access to the Organization's allocated credits.

Actual Behavior

PATs appear to be associated with the Free account and only have access to the Free-tier credit allocation.

Can someone confirm whether PATs are expected to inherit Organization credits, or if there is a separate process required to create Organization-scoped API credentials?