Files
threshold/website/content/docs/commands/scopes/create.mdx
T
Dan HeathandRobin Beck b442c1fa60 docs: Update meta content - CLI (#5343)
* docs: Update meta content - CLI

* docs: Edits for consistency

* docs: More edits for consistency

* Apply batch of suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* Apply batch suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* docs: Remove given id references

* Update read.mdx

* Update read.mdx

---------

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
2024-12-17 14:13:18 -05:00

44 lines
1.3 KiB
Plaintext

---
layout: docs
page_title: scopes create - Command
description: >-
The "scopes create" command creates a new scope resource.
---
# scopes create
Command: `scopes create`
The `scopes create` command lets you create a new scope.
## Example
This example creates a scope with the name `prodops` and the description `Scope for ProdOps`:
```shell-session
$ boundary scopes create -name prodops -description "Scope for ProdOps"
```
## Usage
<CodeBlockConfig hideClipboard>
```shell-session
$ boundary scopes create [options] [args]
```
</CodeBlockConfig>
### Command options
- `-description=<string>` - The description to set on the scope.
- `-name=<string>` - The name to set on the scope.
- `-scope-id=<string>` - The scope in which you want to create the scope.
The default is `global`.
You can also specify the scope using the **BOUNDARY_SCOPE_ID** environment variable.
- `-skip-admin-role-creation` - If set, Boundary does not create a role that grants the current user administrative access to the newly created scope.
The default value is `false`.
- `-skip-default-role-creation` - If set, Boundary does not create a role that grants the anonymous user access to log in to auth methods and other actions within the newly created scope.
The default value is `false`.
@include 'cmd-option-note.mdx'