Jeff Escalante
0469f46252
* add bugsnag and segment keys * convert to next-mdx-remote * app layout adjustment * client transitions for subnav * correct release notes structure * remove unneeded files * update deps to fix jump to section bug, remove cache clear from start command
22 lines
619 B
Plaintext
22 lines
619 B
Plaintext
---
|
|
layout: docs
|
|
page_title: Configuration
|
|
sidebar_title: Action
|
|
description: |-
|
|
The annatomy of a Boundary action
|
|
---
|
|
|
|
# Action
|
|
|
|
An action is a defined capability within the Boundary system. Each Resource Type defines its own set of Actions. Currently, the union of actions from all Resource Types is: create, read, update, delete, list, connect. This is not a fixed list and no design or implementation should assume it will ever be a fixed list.
|
|
|
|
## Attributes
|
|
|
|
For information on how actions are constructed into grant strings, see the [grants]() section.
|
|
|
|
## Referenced By
|
|
|
|
- [Grant]()
|
|
- [Resource]()
|
|
- [Role]()
|