Documentation

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Entity API / checkPermissions

Operation Information

  • Application Reference: com.hornbill.boardmanager
  • Scope: Entity - Board
  • Class: Entity
  • Required Privilege Level: user
  • Required Rights: Group A - canView

Description

Check the permissions on the board for the specified user. The flowcode will throw an exception if an input permission is not allowed.

Request Parameters

The checkPermissions API takes the following input parameters.

Note

When sending a JSON request payload to the API, the order of parameters is not significant. However, for XML request payloads, parameters must be provided in the exact order specified in this documentation to comply with input validation requirements.

Name Type Required Description
boardId xs:string No Board Id to check Permissions for
cardId xs:string No The card Id (used to get board Id if the board Id isn't supplied)
canView xs:boolean No Can view the board
canMove xs:boolean No can Move cards on Board
canUpdate xs:boolean No Can Update Cards
canAdd xs:boolean No can Add and remove cards
canShare xs:boolean No can Share and set permissions
canDesign xs:boolean No Can create and remove columns and change column configuration

Response Parameters

Name Type Description
mask xs:string permissions mask
canView xs:boolean True if the user can view this board
canMove xs:string True if the user can move cards
canUpdate xs:string True if the user can update card
canAdd xs:string True if the user can Add or Remove cards
canShare xs:string True if the user can share the board
canDesign xs:string True if the user can design the board

Code Examples

In This Document