List the times staff entered this team
const url = 'http://localhost:8000/api/team/staff-access/';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:8000/api/team/staff-access/ \ --header 'Authorization: Bearer <token>'Every entry of a staff member (a platform admin) into the active team, newest first: who, when and the reason they gave, which the switch requires (#2749). Staff never become members, so they are not on the roster; this is where their visits show. Paginated with the standard { results, count, next, previous } envelope (limit / offset, default 50, max 200).
Auth: the team’s owner (staff can read it too). A member gets 403.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Number of results to return per page.
The initial index from which to return the results.
Responses
Section titled “Responses”object
One time staff (a platform admin) entered this team (#2749): who, when and the reason they gave. The staff member’s email stays in our own record; the owner sees the name.
object
Entry UUID.
The staff member’s display name, or empty when the account has none (never the email).
Why they entered, in their own words.
When they entered.
Examples
A staff entry
{ "count": 123, "next": "http://api.example.org/accounts/?offset=400&limit=100", "previous": "http://api.example.org/accounts/?offset=200&limit=100", "results": [ { "id": "6f0d1c2b-3a49-4e8f-9b1a-2c3d4e5f6a7b", "staff_name": "Alex Morgan", "reason": "Support ticket 4812: the coach's upload is stuck in processing.", "created_at": "2026-11-02T09:14:00Z" } ]}object
Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).
Example generated
{ "detail": "example"}object
Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).
Example generated
{ "detail": "example"}