Topolo Docs Topolo Platform
Open workspace

Get my hiring-team role

Read the caller's hiring-team role in this workspace (recruiter, hiring_manager, interviewer, or null) and the Recruit actions it allows. Workspace owners and organization admins are always recruiters. Hiring managers see only the roles they manage and their candidates; interviewers see only the candidates they are assigned to interview.

Outcome

Read the caller's hiring-team role in this workspace (recruiter, hiring_manager, interviewer, or null) and the Recruit actions it allows. Workspace owners and organization admins are always recruiters. Hiring managers see only the roles they manage and their candidates; interviewers see only the candidates they are assigned to interview.

Before you start

  • Verify identity and the pinned organization context, then discover the exact action and a granted Recruit workspace.
  • The required application permission is workspace:read. Hiring-team roles and record visibility are enforced separately; a workspace grant alone does not grant every Recruit action.
  • Organization and workspace identity come from verified context. Pass the workspace as resourceType/resourceId, separate from action input; request-body organizationId/workspaceId values cannot select an authorized scope.
  • The first authorized action can initialize an identity-only workspace mirror and invoke the configured workspace-created callback. It does not create an Auth workspace or grant new access.

Recruiters can perform the full hiring workflow. Hiring managers see their managed roles and candidates; interviewers see assigned interviews and their candidates. Workspace owners and organization administrators act as recruiters. Use team.me to read the caller's effective role and allowed actions.

Discover the target

topolo whoami --json
topolo actions get app_topolo_recruit.team.me --detail --json
topolo resources topolo-recruit --json
topolo workspaces list topolo-recruit --json
topolo actions get app_topolo_recruit.team.me --detail --json

Request

GET /api/team/me

Save input as payload.json. CLI and MCP action input includes path identifiers. The reviewed plan separates path/query fields from the HTTP body. Set RECRUIT_WORKSPACE_ID from granted resource discovery.

Inspect and test this action in the signed action console. Use its discovered schema and plan; a test response still requires the verification described below.

Input fields

Use an empty JSON object as input; verified credential and workspace context are separate.

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Effects

  • Reads the caller's role without changing state.

Interpret the response

Confirm $.me.userId is the calling identity.

The response identifier path is $.me.userId for team_member. Lists may be empty; an empty list is not a discovered target.

Exact success schema:

{
  "type": "object",
  "required": [
    "me"
  ],
  "properties": {
    "me": {
      "type": "object",
      "properties": {
        "userId": {
          "type": "string"
        },
        "teamRole": {
          "type": [
            "string",
            "null"
          ]
        },
        "allowedActions": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      }
    }
  }
}

Worked examples

Actual dispatcher and migration-created SQLite or Worker handlers; Auth/workspace identity, object storage, mail and Notify dependencies are simulated. These synthetic fixtures establish no live authorization or delivery. A synthetic fixture identifier grants no access. Validate and inspect the planned request before executing. Commands with --confirm or MCP confirm:true assume the intended effect or data export has already been authorized.

Successful request

Actual dispatcher and migration-created SQLite; verified Auth/workspace context, object storage, mail and Notify dependencies are simulated. No live delivery or credential authorization is established. This complete response is a local fixture, not a deployed or delivered result.

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_recruit.team.me --data @payload.json --json
topolo actions plan app_topolo_recruit.team.me --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.team.me --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_recruit.team.me",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "me": {
    "userId": "u_owner",
    "teamRole": "recruiter",
    "allowedActions": [
      "widget.get",
      "workspace.bootstrap",
      "team.me",
      "team.list",
      "team.members.set",
      "team.members.remove",
      "settings.get",
      "settings.update",
      "job_board.get",
      "job_board.update",
      "job_board.publish",
      "job_board.unpublish",
      "reports.overview",
      "roles.list",
      "roles.get",
      "roles.create",
      "roles.update",
      "roles.open",
      "roles.approve",
      "roles.pause",
      "roles.close",
      "roles.versions.list",
      "candidates.list",
      "candidates.import",
      "candidates.get",
      "candidates.create",
      "candidates.update",
      "candidates.archive",
      "candidates.merge",
      "candidates.documents.list",
      "candidates.documents.upload",
      "candidates.documents.get",
      "applications.create",
      "roles.stages.update",
      "applications.list",
      "applications.get",
      "applications.move",
      "applications.reject",
      "applications.withdraw",
      "candidates.notes.list",
      "candidates.notes.create",
      "email_templates.list",
      "email_templates.create",
      "email_templates.update",
      "email_templates.archive",
      "candidates.emails.list",
      "candidates.emails.send",
      "event_delivery.status",
      "event_delivery.connect",
      "event_delivery.rotate",
      "event_delivery.disconnect",
      "interviews.list",
      "interviews.get",
      "interviews.schedule",
      "interviews.update",
      "interviews.cancel",
      "scorecards.get",
      "scorecards.save",
      "scorecards.submit",
      "scorecards.list",
      "decisions.list",
      "decisions.record",
      "offers.list",
      "offers.get",
      "offers.create",
      "offers.update",
      "offers.send",
      "offers.respond",
      "offers.withdraw",
      "reports.funnel",
      "candidates.export",
      "candidates.erase",
      "retention.status"
    ]
  }
}

HTTP 200. Confirm $.me.userId is the calling identity.

Another supported request

Actual dispatcher and migration-created SQLite; verified Auth/workspace context, object storage, mail and Notify dependencies are simulated. No live delivery or credential authorization is established. This complete response is a local fixture, not a deployed or delivered result.

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_recruit.team.me --data @payload.json --json
topolo actions plan app_topolo_recruit.team.me --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.team.me --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_recruit.team.me",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "me": {
    "userId": "u_admin",
    "teamRole": "recruiter",
    "allowedActions": [
      "widget.get",
      "workspace.bootstrap",
      "team.me",
      "team.list",
      "team.members.set",
      "team.members.remove",
      "settings.get",
      "settings.update",
      "job_board.get",
      "job_board.update",
      "job_board.publish",
      "job_board.unpublish",
      "reports.overview",
      "roles.list",
      "roles.get",
      "roles.create",
      "roles.update",
      "roles.open",
      "roles.approve",
      "roles.pause",
      "roles.close",
      "roles.versions.list",
      "candidates.list",
      "candidates.import",
      "candidates.get",
      "candidates.create",
      "candidates.update",
      "candidates.archive",
      "candidates.merge",
      "candidates.documents.list",
      "candidates.documents.upload",
      "candidates.documents.get",
      "applications.create",
      "roles.stages.update",
      "applications.list",
      "applications.get",
      "applications.move",
      "applications.reject",
      "applications.withdraw",
      "candidates.notes.list",
      "candidates.notes.create",
      "email_templates.list",
      "email_templates.create",
      "email_templates.update",
      "email_templates.archive",
      "candidates.emails.list",
      "candidates.emails.send",
      "event_delivery.status",
      "event_delivery.connect",
      "event_delivery.rotate",
      "event_delivery.disconnect",
      "interviews.list",
      "interviews.get",
      "interviews.schedule",
      "interviews.update",
      "interviews.cancel",
      "scorecards.get",
      "scorecards.save",
      "scorecards.submit",
      "scorecards.list",
      "decisions.list",
      "decisions.record",
      "offers.list",
      "offers.get",
      "offers.create",
      "offers.update",
      "offers.send",
      "offers.respond",
      "offers.withdraw",
      "reports.funnel",
      "candidates.export",
      "candidates.erase",
      "retention.status"
    ]
  }
}

HTTP 200. Confirm $.me.userId is the calling identity.

Verify the result

  • Confirm $.me.userId is the calling identity.

Errors and recovery

  • organization_context_required (HTTP 403): Select the organization authorized by the credential; do not send an organization id in the action input.
  • permission_denied (HTTP 403): Grant the credential the required Recruit workspace permission.
  • workspace_required (HTTP 409): Create a Recruit workspace, or pass the workspace resource context.
  • invalid_input (HTTP 422): Correct the fields named in error.details using inputSchema, then retry.

Authentication or gateway failures may occur before the Recruit handler. Preserve the exact discovered service error, request id and credential context. The local fixtures do not establish live credential authorization.

Recovery boundary

This action does not change service state.

Evidence

Actual dispatcher and migration-created SQLite or Worker handlers; Auth/workspace identity, object storage, mail and Notify dependencies are simulated. These synthetic fixtures establish no live authorization or delivery. Test capture provenance is retained with each fixture. API, database and integration outcomes require separate verification in the target environment.