> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Grant or revoke Projects boards access on one membership

> Sets the two Projects boards entitlements (`boards.personal`, `boards.shared`) on ONE user–institution membership row. Allowed to a super admin, an administrator of that institution (`institutions.edit`), or a manager of the institution's account. The row must exist and be active (enrol the person first); only the two entitlement strings are written, nothing else on the row changes. A non-super cannot change a super admin's rights. Design: docs/plans/2026-10-06-boards-account-entitlements-design.md (D6).




## OpenAPI

````yaml /mdx/api-reference/admin/admin-api.json put /api/admin/boards/access
openapi: 3.0.0
info:
  title: Pria Admin API
  version: 2.0.236
  description: >-
    Pria API Documentation Praxis's developer platform is a core part of our
    mission to empower organizations to grow better. Our APIs are designed to
    enable teams of any shape or size to build robust integrations that help
    them customize and get the most value out of Pria. All Pria APIs are built
    using REST conventions and designed to have a predictable URL structure.
    <br/>  <br/>They use many standard HTTP features, including methods (POST,
    GET, PUT, DELETE) and error response codes.  <br/> <br/>All API calls are
    made under https://hiimpria.ai/api and all responses return standard JSON.
    In these docs, you'll find lists of all available endpoints for a given API,
    along with interactive code blocks for building requests. For walkthroughs
    of basic usage for these APIs, check out the API guides. <br/> <br/>A
    session that a course page (Canvas) opened for an administrator — or that a
    Digital Twin's sign-in provider opened for one of its people — starts with
    user rights in that twin only: until the person confirms it's them with a
    code (POST /api/user/launch-scope/challenge, then /api/auth/mfa-resend and
    /api/auth/mfa-verify), every route outside that twin's day-to-day work
    answers 403 with code LAUNCH_SCOPE_STEP_UP and the twin's id.
servers:
  - url: https://pria.praxislxp.com
    description: Pria API Server
security: []
tags:
  - name: Authentication
    description: User authentication, registration, and password management (/api/auth)
  - name: OAuth
    description: OAuth authentication providers - Google, GitHub, SSO (/api/auth/oauth)
  - name: User
    description: User profile management and account operations (/api/user)
  - name: User Institutions
    description: User institution memberships and switching (/api/user/institution)
  - name: User Tools
    description: Available tools for authenticated users (/api/user/tools)
  - name: Institutions
    description: Institution settings and configuration (/api/user/institution)
  - name: Conversation
    description: AI conversation and Q&A endpoints (/api/ai)
  - name: Realtime
    description: Real-time voice AI and WebRTC sessions (/api/ai/rt)
  - name: Assistant
    description: AI assistant configuration and management (/api/user/assistant)
  - name: History
    description: Conversation history and favorites (/api/user/history)
  - name: RAG
    description: >-
      Document upload, embedding, and retrieval-augmented generation
      (/api/user/files, /api/user/rag)
  - name: Setting
    description: Instance variables and settings management (/api/user/setting)
  - name: Branding
    description: Digital twin branding and customization (/api/agent/branding)
  - name: Agent
    description: Agent engagement and session management (/api/agent)
  - name: SDK Launch
    description: >-
      SDK launch token signing and verification for secure iframe embedding
      (/api/auth/sdk-sign, /api/auth/sdk-verify)
  - name: Testing
    description: Health checks, diagnostics, and test endpoints (/api/test)
  - name: Admin Accounts
    description: Account management for super admins (/api/admin/account)
  - name: Admin Institutions
    description: Institution management for admins (/api/admin/institution)
  - name: Admin Users
    description: User management for admins (/api/admin/user)
  - name: Admin Entitlements
    description: >-
      User-institution relationships and permissions
      (/api/admin/userInstitution)
  - name: Admin Sessions
    description: Session management for admins (/api/admin/session)
  - name: Admin Histories
    description: Conversation history management and analytics (/api/admin/history)
  - name: Admin Assistants
    description: AI assistant management for admins (/api/admin/assistant)
  - name: Admin Questions
    description: Institution question and prompt management (/api/admin/question)
  - name: Admin Tools
    description: Tool configuration management (/api/admin/tool)
  - name: Admin AI Models
    description: AI model configuration (/api/admin/aimodel)
  - name: Admin MCP Servers
    description: Model Context Protocol server management (/api/admin/mcpserver)
  - name: Admin Feedbacks
    description: User feedback management (/api/admin/feedback)
  - name: Admin Uploads
    description: Upload management (/api/admin/upload)
  - name: Admin Charts
    description: Analytics and visualization chart management (/api/admin/chart)
  - name: Admin Memory
    description: Admin inspection and editing of user/instance memory parameters.
  - name: Admin Usage Limits
    description: Per-user usage-vs-cap reporting and account-wide at-limit counts.
paths:
  /api/admin/boards/access:
    put:
      tags:
        - Admin Boards
      summary: Grant or revoke Projects boards access on one membership
      description: >
        Sets the two Projects boards entitlements (`boards.personal`,
        `boards.shared`) on ONE user–institution membership row. Allowed to a
        super admin, an administrator of that institution (`institutions.edit`),
        or a manager of the institution's account. The row must exist and be
        active (enrol the person first); only the two entitlement strings are
        written, nothing else on the row changes. A non-super cannot change a
        super admin's rights. Design:
        docs/plans/2026-10-06-boards-account-entitlements-design.md (D6).
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - personal
                - shared
              properties:
                userInstitutionId:
                  type: string
                  description: >-
                    The membership row id. Either this, or userId +
                    institutionId.
                userId:
                  type: string
                institutionId:
                  type: string
                personal:
                  type: boolean
                  description: >-
                    Grant (true) or revoke (false) the personal Projects
                    workspace.
                shared:
                  type: boolean
                  description: >-
                    Grant (true) or revoke (false) the institution's shared
                    Projects workspace.
      responses:
        '200':
          description: The resulting flags
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  userInstitutionId:
                    type: string
                  personal:
                    type: boolean
                  shared:
                    type: boolean
        '400':
          description: Flags not booleans, or identifiers missing / invalid
        '401':
          description: Unauthorized
        '403':
          description: The caller may not grant on this institution
        '404':
          description: Membership or institution not found
        '409':
          description: The membership is not active
      security:
        - apiKeyAuth: []
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-access-token
      description: JWT token passed in x-access-token header

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.