> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/documentation/settings.md).

# Settings

Settings in Rewst are robust and can be configured however you desire. This menu governs organization-level configuration and is organized into tabs, each with their own submenus. Navigate to **Settings** in the left side menu of your Rewst platform to access the tabs listed in this matrix.

{% hint style="info" %}
Click on any of the menu tab names below to expand and view its documentation.
{% endhint %}

<details>

<summary>General</summary>

This menu is in development. Check back for documentation updates as we proceed with platform release.

</details>

<details>

<summary>Organizations</summary>

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FwOJ8xV6ZwkxyYe2d6W9a%2Fimage%20(95).png?alt=media&amp;token=7fb78bab-9f81-473d-9a7c-57c9d9e39d8f" alt=""><figcaption></figcaption></figure>

The Organizations tab manages the organization hierarchy between your child, customer organizations and your parent, MSP organization. The list contains the current organization's direct child organizations.&#x20;

Click on any of the column headers in the table to filter by organization **Type**, **Status**, or **Created** date. The **Sub-orgs** column shows the number of child organizations nested beneath that organization. Click on the filter buttons to the right of the **Search organizations** field to expand and select additional search filter criteria.

#### Manually create a new organization in Rewst

{% hint style="warning" %}
Remember, organizations— orgs for short— are divided up into parent and child organizations. Every new customer you onboard into Rewst will need its own separate child org.
{% endhint %}

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FegYD5uKPiAUyUYgMI8YD%2FScreenshot%202026-10-21%20at%2010.23.15%E2%80%AFAM.png?alt=media&amp;token=c9bf512f-bb3b-42c1-95ac-b1d000b250f5" alt=""><figcaption></figcaption></figure>

1. Navigate to **Settings** **> Organizations**.
2. Click **+ Add Sub-Org**.
3. Fill out the following fields in the **Add Sub-Org** dialog that appears:
   1. **Organization Name**: This is the display name for the organization - keep it short and recognizable, and avoid special characters
   2. **Organization Type**:&#x20;
   3. **First User Email (optional)**: Fill in this field if you want an admin user to be created. They will be able to sign in using their email and a verification code emailed to that listed address.
   4. **First User Role**: Use this drop-down selector to create an admin user or owner user. They can sign in using their email and a verification code. Only an owner can grant the owner role.
   5. **Metadata (JSON, optional)**: Use this field to enter optional JSON metadata for custom attributes.
4. Click **Create**.

#### Select an organization

Once an organization is created, it will appear in the organizations list of this organizations menu, as well as the drop-down organizations selector in the top right of the Rewst platform.

<div align="left"><figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FlRodJcY3RLKs7g5hTE7E%2FScreenshot%202026-09-09%20at%2010.44.20%E2%80%AFAM.png?alt=media&amp;token=8b215ede-7d12-4ab8-88a0-2e502fca0e92" alt=""><figcaption><p>Click ⌄ to expand your organization selector</p></figcaption></figure></div>

#### Delete an organization

{% hint style="danger" %}
Once an organization is deleted, it can’t be brought back, even by Rewst support. Make sure that you intend to delete an organization permanently before proceeding with the following steps.
{% endhint %}

1. Click **...** next to the organization you wish to delete. This will expose the additional options submenu.
2. Click **Delete**.
3. Confirm that you wish to delete the organization in the dialog that appears.
4. Note that the **Recently Deleted** filter in the menu only appears after your org has been deleted, or if an org has been recently deleted.

#### Move an organization

1. Click **...** next to the organization you wish to move.
2. Click **Move**.
3. Choose the new parent org for your selected org. Note that moving this org also moves any orgs nested beneath it.
4. Click **Move**.

</details>

<details>

<summary>Integrations</summary>

The Integrations tab is a shortcut to the total Integrations menu. View its documentation [here](https://docs.rewst.help/rewst-documentation/documentation/integrations.md).

</details>

<details>

<summary>Credentials</summary>

The Credentials tab is a shortcut to the total credentials menu. View its documentation [here](https://docs.rewst.help/rewst-documentation/documentation/credentials.md).&#x20;

</details>

<details>

<summary>Universal Nodes</summary>

The Universal Nodes tab contains settings for what runs each universal node for the selected organization. While these actions will appear in your Workflow Builder before setup, the Send SMS action will fail until setup is complete, and the Send Email action will fall back to the first generation, non-universal [Send Email action](https://docs.rewst.help/pages/27ztelCxRCWn8lmMEtvh#send-email-tasks.send_email).

Saving replaces any earlier setup of these actions completely. Click **remove** to delete the setup, after which point the action's steps fail until set up again.

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FIrMYjUvjajVJwaTNNSbu%2FScreenshot%202026-11-13%20at%2011.39.14%E2%80%AFAM.png?alt=media&amp;token=1ac85ce4-ff4d-4f66-9140-e71d8a2364f4" alt=""><figcaption></figcaption></figure>

**Send SMS**&#x20;

Send a text message through the provider your org sets up in this menu. See our full documentation on the action [here](https://docs.rewst.help/rewst-documentation/documentation/automations/nodes/nodes-actions.md#send-sms). We recommend reading through that documentation first to determine how you would like to set up the universal node.&#x20;

To set up, choose between two possible send through settings:

* An integration operation: the integration/provider your org uses to send text messages, then the operation that sends one. If your org has none, install one or build a custom integration first. The list of available operations will differ depending on which integration you choose.
  * After saving, you can send one real text to a number you choose, to confirm it works. Test send is available for integration setups only, not published-workflow setups.
* A published workflow of this org: use the **Published workflow** drop-down selector to choose which published workflow to use. Only your current org's own workflows published as a node will be listed, not parent organizations' workflows. Choose this option when you build a custom workflow that sends texts.

{% hint style="info" %}
If you manage child organizations underneath yours:

* No grant - default: your workflows send texts through your setup, even when they're working for a customer.
* Grant to a customer organization: when your workflows work for that customer, they use the customer's own Send SMS setup instead. The customer has to have finished their own setup.
* A customer's own workflows never use your setup.

To set up a customer's own Send SMS, you have to switch into that customer's organization first.
{% endhint %}

**Send Email**&#x20;

Send an email through the provider your org sets up in this menu. See our full documentation on the action [here](https://docs.rewst.help/rewst-documentation/documentation/automations/nodes/nodes-actions.md#send-email). We recommend reading through that documentation first to determine how you would like to set up the universal node.&#x20;

To set up, choose between two possible send through settings:

* An integration operation: the integration/email service your org uses to send text emails, then the operation that sends one. If your org has none, install one or build a custom integration first. The list of available operations will differ depending on which integration you choose.
* A published workflow of this org: use the **Published workflow** drop-down selector to choose which published workflow to use. Only your current org's own workflows published as a node will be listed, not parent organizations' workflows.
  * A published workflow can't send attachments.

Before saving, Rewst warns you about two things:

* Your default changes: Send Email steps in your workflows that don't name an email account will now use this service instead of Rewst's built-in default. That includes your workflows that run for customer organizations below you, unless a grant points them elsewhere. Workflows owned by other organizations don't change.
* No attachments, shown only when attachments are off: steps that include files will fail.

{% hint style="info" %}
If you manage child organizations underneath yours:

* No grant - default: your workflows send emails through **your** setup, even when they're working for a customer.
* Grant to a customer organization: when your workflows work for that customer, they use the customer's own Send Email setup instead. The customer has to have finished their own setup.
* A customer's own workflows never use your setup.

To set up a customer's own Send Email, you have to switch into that customer's organization first.
{% endhint %}

</details>

<details>

<summary>Auth Methods</summary>

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2Fw4bbEBHeOmOApUWha9Rs%2FScreenshot%202026-08-20%20at%204.44.14%E2%80%AFPM.png?alt=media&amp;token=5aacd47f-43b6-4ac8-8d7b-f43f47f40e0b" alt=""><figcaption></figcaption></figure>

The Auth Methods tab defines authentication templates for credentials, including custom templates for vendor-specific authentication flows. The Platform Auth Methods section lists the built-in templates that come stock in the platform and can't be modified. Each entry is tagged with its authentication type and, where relevant, the vendor it was built for.

* Custom auth methods are defined in your own organization.
* Platform auth methods are built by Rewst and available to everyone.&#x20;

</details>

<details>

<summary>SSO (Single Sign On)</summary>

The SSO tab configures OIDC single sign-on for the organization, and lets your people log into Rewst with your existing company login instead of a separate Rewst password.&#x20;

#### OIDC Configuration

* **Redirect URI** - Rewst generates this and gives you a copy button - you\
  paste it into your identity provider's configuration
* **Identity Provider** - select your identity provider to customize field labels and ordering
* **IdP Issuer URL** - the OIDC issuer URL must serve a .well-known/openid-configuration endpoint
* **Client ID** - The application identifier your provider issues to Rewst
* **Client Secret** -the client secret value
* **Default Role** - set what new role users receive on first SSO login
* **Default MSP Role** - optional MSP-provided role to grant automatically when a qualifying user first signs in via this tenant
* **Auto-provision users -** control whether new users are created automatically on sign-in
* **Allowed email domains** - Comma-separated list of email domains allowed to auto-provision new users via SSO, which should be left empty to block auto-provisioning for every domain&#x20;

#### Domain Verification

Verify ownership of email domains to restrict the SSO login.&#x20;

* Click **Add Domain** to add a new domain
* Click **Refresh** to manually push sync the domain
* Click **Remove** to remove a domain after it has been added to the list

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FIqXRzLbhX3Qc4G8wqA3u%2FScreenshot%202026-09-18%20at%202.45.01%E2%80%AFPM.png?alt=media&amp;token=8cc781f5-8485-4f65-8b8f-647c60e90fa5" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>Custom domains</summary>

The custom domains tab contains a list of all your custom domains served on published apps and forms. Note that you need to be an org admin to see all buttons and options in this tab.

You'll need to prove you own the domain once, with a DNS record. A custom domain only changes the address, not who can get in. A public app or form opens for anyone, and anything limited to signed-in people sends visitors to the Rewst login first. An app shared by a generated link can't be routed to a custom domain. Forms can share one hostname, one form per path, but are limited by IP address.

* A hostname is an address under the domain, such as portal.example.com, that serves an app or form.
* Ownership indicates if the domain has been verified or is still pending verification.
* Hostname status lists the number of host names, if a host name has been declared at all, and if the host name is active.

To add a custom domain:

1. Click **Add Domain**.
2. Enter the domain in the dialog that appears.
3. Click **Continue**.
4. Rewst gives you a TXT record name and value. Copy both values and store them someplace secure.
5. Add the copied TXT record at your DNS provider **-** Cloudflare, GoDaddy, Route 53, etc.:
   * Type: `TXT`
   * Name: enter it exactly as Rewst shows it. Rewst gives it without a trailing dot, and most providers want it that way. Some providers add your domain to the name automatically, so enter only the part before the domain. In a raw zone file, add the trailing dot yourself.
   * Value: enter the value exactly.
6. Once the record is published, return to Rewst.
7. Click **Check now**. If DNS hasn't caught up yet, you'll get a message saying so; wait a bit and check again.
8. Click **Manage** to the right of your relevant domain in the domain list.
9. Click **Show DNS record**. If DNS hasn't caught up yet, you'll get a message saying so; wait a bit and check again.
10. Click **Add hostname** to the right of your relevant domain in the domain list to add a hostname on the verified domain, such as `portal.example.com`. Rewst gives you a CNAME record to publish at your DNS provider.
11. Route the hostname to your app or form. An app uses the whole hostname (path `/`). Do this right away: a hostname with no route to a published app or form never goes active.
12. Wait for it to go active. DNS and the security certificate take some time to set up. Once active, the app or form will go live at your address.

</details>

<details>

<summary>Users</summary>

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2F3FbzuITkEMnF4VFJPoVm%2FScreenshot%202026-08-20%20at%204.45.06%E2%80%AFPM.png?alt=media&amp;token=546f67a1-4c38-41ab-8917-49edca11937c" alt=""><figcaption></figcaption></figure>

A *user* in Rewst is an individual. That individual will be allowed to interact with Rewst in some way, as dictated by their role. Users should not be confused with [organizations](#organizations). The Users tab manages people and access for the organization. Filter users by search, status, and sign-in method, along with the inclusion or exclusion child-tenant users. Each row lists the user's email, name, assigned roles, status, sign-in method, home tenant, last login, and creation date, with an actions menu for each entry.

### Add and remove users from Rewst

Adding users into Rewst allows them access to build workflows, view forms, or update configuration items, like integrations or organization variables. When adding a user, you'll select their role from either the Rewst pre-set roles, or any custom roles that you have already set up. Learn more about roles and how to manage them [here](#roles).&#x20;

#### Add a user to an organization

Note that new users need an initial role in the organization before they can sign in. To give a user at your organization access, first double check that the selected organization in the org selector is set to your desired organization.&#x20;

1. Navigate to **Settings > Users**.
2. Click **Add User**.
3. Enter the **Name** and **Email** of the user into the respective fields. Email is only necessary if you are planning to use the email code option.
4. Select their role from the list in the **Roles** drop- down selector.
5. Choose the **Sign-in type** from the drop-down selector:
   1. Password setup link - after creation, a dialog will appear with a link to copy for manual sharing
   2. Email code - after creation, an email will be sent to the user
   3. SSO only - only available after [SSO has been configured](#sso-single-sign-on). After creation, the user will have the role you applied in the previous step when they log in. Note: SSO can be configured to auto-provision users upon sign in with a specified default role.
6. Click **Create user**.\
   \
   ![](https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FJTmyjBKYoLvnoPMgiOom%2FScreenshot%202026-09-21%20at%203.32.10%E2%80%AFPM.png?alt=media\&token=99e76e49-7568-403f-8466-a7f1df69dd78)<br>

#### Edit a user's role

1. Navigate to **Settings > Users**.
2. Find your desired user in the Users list.&#x20;
3. Click .**.. > Manage roles**.&#x20;
4. Click **Remove** to the far right of the user's record to remove the user's existing role. This will not delete the user. Their other roles will remain, and they'll stay connected to this organization.
5. If you wish to add another role to the user:
   1. Select a role from the **Role to add** drop-down selector, or
   2. Give the user a role in the customer organizations under this current org, without creating a separate account in each org, via the **Roles in customer orgs** drop-down selector
      1. Check the **All customer orgs** checkbox to apply this to every customer org, even orgs created after this settings update
6. Click **Done**.

#### Remove a user&#x20;

{% hint style="warning" %}
If needed, re-add a removed user by inviting them again. Removing a user won’t remove any workflows they’ve built or delete any activity in the platform, such as results of workflows or edits they made to forms.
{% endhint %}

1. Navigate to **Settings > Users**.
2. Find your desired user in the Users list.&#x20;
3. Click .**.. > Delete**.&#x20;
4. Confirm that you want to **Delete** in the confirmation dialog that appears. The user will will lose access to this organization and disappear from the active users list. This can't be undone from the UI.

</details>

<details>

<summary>Roles</summary>

The Roles tab defines scoped permission bundles for assignments and templates. A *role* is a named set of "can do this, can't do that." You build them here, then assign them to individuals in the [users](#users) part of the settings menu. System roles are created by Rewst and can't be edited. Create custom roles when you need a narrower permission bundle for a team, organization, or external identity.

The stock, Rewst-set role catalog currently includes:

| Role   | Description                                                                                                                | Permissions                                      |
| ------ | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
| Admin  | Full admin control in this organization. Descendants do not inherit Admin from this role, only Owner cascades that access. | 84                                               |
| Editor | Build and run automations without tenant governance write access.                                                          | 67                                               |
| Owner  | Full control in this organization and every descendant organization. Owner access cascades down the organization tree.     | 1, represented as a wildcard covering everything |
| Viewer | Read-only access to all tenant-visible features.                                                                           | 32                                               |

Each role has a **View** option that opens its full permission list.

### Add a role

1. Navigate to **Settings > Roles.**
2. Click **Add role**.
3. Give your role a clear, unique name.
4. Enter an explanation for who should use this role and what it is for into the **Description** field.
5. Check off boxes for all desired permissions for this role. Use the **Find permissions** search bar to narrow down the list by resource or permission key.&#x20;
6. Click **Create role**.

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FXMmQigVfUX5agcEBo0hh%2FScreenshot%202026-09-21%20at%203.48.17%E2%80%AFPM.png?alt=media&amp;token=c5787940-2771-4879-9307-6eddc9a4af74" alt="" width="563"><figcaption></figcaption></figure>

### Edit a role

{% hint style="info" %}
If you simply need to view existing permissions for a role, click **View** instead of edit.
{% endhint %}

1. Navigate to **Settings > Roles.**
2. Scroll down the **Role catalog** list until you find your desired role.
3. Click **Edit**.
4. Make changes to your role's settings as desired.
5. Click **Save changes**.

### Delete a role

1. Navigate to **Settings > Roles.**
2. Scroll down the **Role catalog** list until you find your desired role.
3. Click **Delete**.

### Make role available to child organizations

This doesn't apply to users in the current organization, because local users can already be assigned the role directly here. Scope stays on the availability, not the role itself.

1. Navigate to **Settings > Roles.**
2. Scroll down the **Role catalog** list until you find your desired role.
3. Click **Make available**.
4. Check **All customer tenants** to set that current and future descendants of this organization can use this role. Leave unchecked if you do not want this setting applied.
5. Pick one or more descendants that should see this role. You may also choose this via previously made tags.&#x20;
6. Click **Save availability.**&#x20;
7. Any settings from previous modifications will appear in the **Current availability** section of the dialog.

</details>

<details>

<summary>Teams</summary>

The teams tab is for grouping people together so that access can be granted to\
a group rather than repeated person by person. From this tab, create a team, refresh the directory, and manage the membership and roles of a team.

{% hint style="info" %}
Note that assigning roles to a team is gated separately from creating and editing teams. It is possible to have permission to manage teams while not having permission to assign roles to them, in which case you will see the directory and the create button but not the role controls.
{% endhint %}

### Create a team

1. Navigate to **Settings> Teams**.
2. Click **Add team**.
3. Give your team a clear, unique name.
4. Enter an explanation for who is on this team and what they own into the **Description** field.
5. Assign the team a color. Use the pre-selected Rewst options or add a custom color via preferred hexcode.
6. Assign the team an icon or choose to have no icon for the team.&#x20;
7. Click **Create team**.

### Manage membership and roles of a team

1. Navigate to **Settings> Teams**.
   1. Click **Manage members**.
      1. Enter a name or email into the **Add member** search field.&#x20;
      2. Click on your desired member from the search results to add them to the list.
      3. Click **Remove** next to the user in the list to remove them from the team.
   2. Click **Manage roles**.
      1. Choose a role to grant to the team from the **Assign a role** drop-down selector.
      2. Any roles previously granted to the team will appear in the **Roles assigned to this team** list. Once you add a role, it too will appear here.&#x20;

</details>

<details>

<summary>Platform Identities</summary>

The Platform Identities tab manages the identities workflows use when they act on Rewst itself as opposed to an external system. If your workflows only reach outward into vendor\
systems, you will rarely need these settings. The tab matters when a workflow needs to perform actions inside Rewst.

Workflows bound to an identity can only perform what its assigned permissions allow. This tab has two distinct permission levels behind it: one for operating an identity, and one for administering it. Two people with access to the same tab may see different controls.

### Create an identity

1. Navigate to **Settings > Platform identities.**
2. Click **Create identity**.
3. Give your identity a clear, unique name.&#x20;
4. Enter an explanation of what the identity will do in the **Description** field.
5. Click **Create identity**.

### Assign roles to an identity

1. Find your desired identity in the identity list.
2. Click **... > Manage roles**.
3. Select a role for the identity from the **Add another role** drop-down selector.
4. Select a role from the **Roles in customer orgs** drop-down selector to assign this identity a parent-owned role in customer organizations. This doesn't enable sign-in or operation eligibility.&#x20;
5. Check **All current and future customer orgs** to set this decision for organizations, even ones created in future. Leave unchecked if you do not want this setting applied.
6. Click **Done**.

### Manage client credentials for an identity

Credentials let the created identity authenticate. They're separate from its Roles, which decide what it's authorized to do.

1. Navigate to **Settings > Platform identities.**
2. Click **... > Client credentials**.
3. View any existing credentials in the dialog that appears.
4. Click **Create client secret**.
5. Copy the secret generated and displayed in the dialog. It will be shown once and can't be retrieved again.
6. Click **Revoke client** to invalidate the secret.
7. Click **Rotate secret** to generate a new secret value.
8. Click **Done** to close the dialog and lose visibility of secret values.

</details>

<details>

<summary>AI Access</summary>

The AI Access tab manages tokens and connected apps that let AI tools reach new Rewst. AI tools connect in one of two ways: a token created and pasted into the tool, or a connected app authorized by signing in. Learn more about MCP functionality in Rewst, including how to use this tab, in our MCP documentation [here](https://docs.rewst.help/rewst-documentation/documentation/rewst-agent/mcp-servers-and-rewst.md).&#x20;

</details>

<details>

<summary>Tags</summary>

The Tags tab manages portable tags for the environment. These labels can travel with assets and installed Crates, and a New tag button creates them alongside a Refresh control and a search field. The table lists each tag's color, name, description, and available actions, and prompts the user to create a tag or install a crate to import its tags when none exist yet. For quick visual reference of categories, tags can be color coded.

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FMlfyHxUSHGHbAusyM9Ry%2FScreenshot%202026-08-20%20at%203.51.49%E2%80%AFPM.png?alt=media&amp;token=f3ecbcf8-e932-4d49-a27b-08f7710a25f3" alt=""><figcaption></figcaption></figure>

### Example use cases for tags

* Give better visual indicators for your long list of automations, not just text. For example, you could choose to make all Powershell workflows red.
* Tags can also be used to mark associations between pieces of a larger workflow. Consider a parent workflow which contains several child workflows and a form. Each piece of that parent workflow could be tagged with one tag. Then, you’d select that tag to isolate everything for just that one workflow, regardless of the pieces you used to create it.
* Try creating tags for the development status of a workflow: In Development, In Testing, In Production, etc. If your MSP has multiple builders on staff, different individuals will know not to edit or experiment on an In Production workflow, which could cause problems for their team.

{% hint style="warning" %}
Bulk editing workflow tags will overwrite all previous tags currently set for those selected workflows.
{% endhint %}

### Add a tag

1. Navigate to **Settings > Tags**.
2. Click **New tag**.
3. Enter a clear, unique name for your tag.
4. Assign the tag a color. Click on the displayed color to expand the color picker, where you may choose from Rewst's preset colors or add your own custom color via hex code.
5. Optionally add a description to provide information for what the tag should be used for.
6. Click **Create tag**.

{% hint style="info" %}
Alternatively, create tags for organizations right from the org settings menu.
{% endhint %}

### Edit a tag

1. Navigate to **Settings > Tags**.
2. Locate your desired tag in the tags list.
3. Click **Edit**.
4. Make any changes as desired.
5. Click **Save tag**.

### Delete a tag

1. Navigate to **Settings > Tags**.
2. Locate your desired tag in the tags list.
3. Click **Delete**.
4. Confirm click **Delete tag**.

</details>

<details>

<summary>Activity</summary>

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FONJvLROi39xvaaaPVsPc%2FScreenshot%202026-08-20%20at%204.31.02%E2%80%AFPM.png?alt=media&amp;token=24a6f98f-a301-4e42-92d0-623c91ba550a" alt=""><figcaption></figcaption></figure>

The Activity tab lets you view a running audit log of user actions and system events across your workspace. Each row in the log represents a single event, such as a user creating or deleting an org variable, along with who triggered it, what it targeted, and whether it succeeded.

Filter log events by time window, or limit results to a specific action type.&#x20;

* Click **Start live tail** to stream new events into the table as they happen instead of requiring a manual refresh.&#x20;
* Click **Export CSV** and **Export NDJSON** to download the current filtered results in those respective formats.
* Click on any record to expand its details: **Event ID**, **Code**, and **Data**.

</details>

<details>

<summary>Data Storage</summary>

The Data Storage tab shows guardrails and usage for the workflow *datastore*, which is where automations keep data between runs. Use it to monitor how much workflow datastore you are consuming and how close you are to hitting the guardrails.&#x20;

It's Workflow-only, meaning the data belongs to workflow execution rather than general application storage, and Guardrails enforced, meaning the limits described below are actively applied rather than advisory.

* Tenant scope covers this organization alone.
* MSP subtree scope is shared across the MSP tenant tree, with descendant organizations able to read and write to it.&#x20;
* Each card breaks its usage down into KV keys and records, alongside a remaining-capacity indicator.
* A Critical guardrails section documents the limits that apply to both scopes:

| Guardrail                      | Limit                                                                                                                                                                      |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Default quota                  | 50 MB per scope, with a warning at 80% usage                                                                                                                               |
| Default KV TTL                 | 86,400 seconds, or one day                                                                                                                                                 |
| KV limits                      | Max value of 32 KB, max TTL of 2,592,000 seconds, max namespace length of 128 characters, max key length of 256 characters                                                 |
| Records limits                 | Max record size of 256 KB, max collection length of 128 characters, max record key length of 256 characters                                                                |
| Records paging and writes      | Page size of 50, capped at 500, and a bulk upsert limit of 1,000 items                                                                                                     |
| Records indexing and filtering | Up to 12 indexed fields, max index field length of 128 characters, max index value length of 256 characters, up to 10 filters, and a max cursor length of 1,024 characters |

* A Usage details section below breaks consumption down further, with Tenant and MSP Subtree views showing the top namespaces, top collections, and top workflow nodes by storage use.&#x20;

</details>

## Profile settings

Additional settings exist for MSP top-level organization users who have been granted permissions for those settings. To access them if you are permissioned to do so, click your profile logo in the top right corner of your screen.

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2F8v7zuTdQhi8pthVEMMBA%2FScreenshot%202026-11-03%20at%2010.58.59%E2%80%AFAM.png?alt=media&amp;token=4a2b7f3a-8580-4f94-961b-4fa240f41d75" alt=""><figcaption></figcaption></figure>

<details>

<summary>Dark or light mode</summary>

Toggle this setting to **Dark** or **Light** mode viewing for your Rewst experience.

</details>

<details>

<summary>Achievements</summary>

This page displays milestones you've reached by building and automating with Rewst.&#x20;

* Your Month in Automation displays the number of automations run in the current month. Click **Set an estimated time per run** to set workflow estimations and begin gracking hours saved.&#x20;
* The Automation submenu contains all your individual milestones, lifetime for your Rewst use.

  * Automator - Ran 100 automations in a month
  * Automation Builder - Ran 1000 automations in a month
  * Automation expert - Ran 5000 automations in a month
  * Automation Powerhouse - Ran 10000 automations in a month
  * Getting Started - Executed 1000 automation steps
  * Node Runner - Executed 10000 automation steps
  * Scale Operator - Executed 100000 automation steps
  * Scale Master - Executed 1000000 automation steps
  * First Crate - Published your first Crate to the Marketplace
  * Crate Builder - Published 5 Crates to the Marketplace
  * Prolific Publisher - Published 10 Crates to the Marketplace
  * Marketplace Veteran - Published 25 Crates to the Marketplace
  * Getting Traction - Your Crates reached 10 installs
  * Growing Reach - Your Crates reached 100 installs
  * Community Favorite - Your Crates reached 500 installs
  * Marketplace Star - Your Crates reached 1000 installs
  * Early Adopters - 5 teams use your Crates
  * Building Community - 25 teams use your Crates
  * Widely Trusted - 100 teams use your Crates
  * Industry Standard - 500 teams use your Crates
  * Verified Publisher - Marked as a verified publisher on the Marketplace
  * Three-Day Streak - Logged in 3 days in a row
  * Week Warrior - Logged in 7 days in a row
  * Monthly Dedication - Logged in 30 days in a row
  * Quarter Streak - Logged in 90 days in a row
  * Year-Round Automator - Logged in every day for a year

</details>

<details>

<summary>Preferences</summary>

Use this page to manage account-level defaults for your Rewst experience.

* The URL format submenu determines the format of URL slugs.
  * Slug - Links will use slug URLs
  * Opaque - Links will use opaque URLs
  * Inherit org default - Links will use the default indicated for the organization
* The Agent notifications setting determines if you get told when the agent finishes or needs you, which allows you to work in another tab without losing track of ongoing builds. Rewst never notifies you about a conversation you're already looking at and groups a burst of updates into one notification. Check **Notify me about agent activity** on or off to show a desktop notification. Your browser will ask for permission for this notification the first time it triggers.&#x20;
* The Agent communication style submenu is used to choose how the Rewst agent presents its replies to you.
  * Detail level
    * Concise - Answers first, with minimal explanation; headers and tables are given only when the content needs them
    * Balanced - The default way the agent communicates in the platform
    * Thorough - Explains what it is doing and why, with more structure
  * Technical depth
    * Plain language - Written for non-technical readers: everyday words, no Rewst internals or raw data unless you ask, and technical details available on request
    * Balanced - The default way the agent communicates in the platform
    * Technical - Shows node types, field paths, identifiers, and payloads freely and assumes familiarity with Rewst

</details>

<details>

<summary>Usage &#x26; Billing</summary>

{% hint style="info" %}
Anyone with the billing view permission can see this page. Changing anything in the page, such as meters, contact, or payment, also requires the billing edit permission.
{% endhint %}

* A Payment Alert Banner will appear at the top of the page if there's a payment problem, such as a failed charge or a grace period. Click **Update payment method** to fix it.
* Summary cards display quick numbers for the current month:
  * Monthly bill so far
  * Billable workflow time
  * Nodes executed - individual workflow steps run
* The Plan Limits submenu displays what your plan allows and how close you are to those limits. Click **Change Plan** to launch the plan upgrade dialog. For all plan limits, a setting of zero indicates that it is unlimited.
  * Workflow definitions - Maximum workflow definitions
  * Concurrent workflow runs - Maximum parallel workflow runs
  * MCP tokens per user - Maximum named MCP tokens per user
  * Webhook requests - Inbound webhook rate limit
  * In-app agent monthly spend - Maximum monthly in-app agent AI spend in USD, across included usage and billed overage
  * Datastore storage - Maximum datastore storage in bytes

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FGgBSKMAGr88jXzejDlEo%2FScreenshot%202026-11-03%20at%2011.14.23%E2%80%AFAM.png?alt=media&amp;token=692ec47c-b384-4852-837a-a3579f6baa67" alt=""><figcaption></figcaption></figure>

* The AI Credits submenu displays funding metrics related to the in-app Rewst Agent. Note that AI inside workflows runs on your own AI key and never uses credits.
  * Available now - The total for what credits you have available to spend now
  * Expiring in the next 14 days - Relevant if you have expiring credits
  * Used this month - The total for what was drawn from credits since the first of the current month
  * Own AI key this month - The total of what was spent on your own AI key
  * Balances - Listed in draw order, where the Agent spends whatever expires soonest and credits that never expire are used last; monthly included amount counts as expiring as month's end and is spent in the same order
* The Usage chart shows usage over a period you choose, with three clickable views that can all be displated via Billable Time, Node Count, or Cost on a Daily, Monthly, or Yearly basis:
  * **Workflow Usage**, which you can switch between billable time, node count, or cost
  * **Daily Agent Cost**, for AI spend each day
  * **Monthly Agent Cost**, for AI spend each month\ <br>

    <figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2Fg45c6jpOmEpPJ9Tvhd3V%2FScreenshot%202026-11-03%20at%2011.12.07%E2%80%AFAM.png?alt=media&amp;token=c1e6da4d-e732-4f7d-8c8a-2641e6a585e7" alt=""><figcaption></figcaption></figure>
* The Usage Meters submenu lets you choose the usage columns included in CSV exports. Click **Save** to save any changes to your preferences. Click **Export CSV** to begin file export with your indicated settings.
  * Workflow runs - Completed workflow executions in the selected period
  * Node executions - Workflow node executions recorded in usage rollups
  * Billable duration - Billable workflow runtime in milliseconds
  * Workflow usage cost - Estimated workflow usage charge using the current plan rate
* The Billing Details submenu displays how you're charged for using Rewst. Costs shown are estimates based on current plan rates:
  * Your Current Plan
  * The monthly fee for that plan&#x20;
  * The usage fee - What you pay for the time your workflows spend running during the current billing period, separate from your fixed monthly fee and from AI agent charges
  * The Rewst Agent usage estimate

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/rewst-documentation/documentation/settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
