diff --git a/configuration/auth/development-tokens.mdx b/configuration/auth/development-tokens.mdx index e07c9c465..f41009b33 100644 --- a/configuration/auth/development-tokens.mdx +++ b/configuration/auth/development-tokens.mdx @@ -41,6 +41,10 @@ This can also be used to generate a token for a specific user to debug issues. Development tokens can be used for testing purposes either with the [Sync Diagnostics Client](https://diagnostics-app.powersync.com), the [test-client](https://github.com/powersync-ja/powersync-service/tree/main/test-client), or your app itself (for development purposes). +### Using with Sync Test + +If you're on PowerSync Cloud, [Sync Test](/tools/powersync-dashboard#sync-test) in the PowerSync Dashboard generates a development token for a user ID and connects a client in your browser with it. You do not need to copy the token. + ### Using with Sync Diagnostics Client The [Sync Diagnostics Client](https://diagnostics-app.powersync.com) allows you to quickly test syncing and inspect a user's SQLite database, to verify that your PowerSync Service configuration and Sync Streams behave as expected. diff --git a/debugging/troubleshooting.mdx b/debugging/troubleshooting.mdx index e9dec2fd8..79db9db79 100644 --- a/debugging/troubleshooting.mdx +++ b/debugging/troubleshooting.mdx @@ -66,6 +66,10 @@ Troubleshooting techniques depend on the type of issue: 4. **Writes to the backend source database are failing:** PowerSync is not actively involved: use normal debugging techniques (server-side logging; client and server-side error tracking). 5. **Updates are slow to sync, or queries run slow**: See [Performance](#performance) +### Sync Test + +If you're on PowerSync Cloud, use [Sync Test](/tools/powersync-dashboard#sync-test) in the dashboard to connect a client as a specific user and inspect it with [PowerSync DevTools](/tools/devtools-overview). + ### Sync Diagnostics Client Access the Sync Diagnostics Client here: [https://diagnostics-app.powersync.com](https://diagnostics-app.powersync.com) @@ -101,14 +105,14 @@ Run one from your app code, or use the **Sync now** action in [PowerSync DevTool The result tells you where to look next: -- **The wait completes, but the data is still missing:** Check that the data was committed to the source database before you created the request, and that the user's Sync Streams include it. To see what the device has synced, use [PowerSync DevTools](/tools/devtools-overview) or the [Sync Diagnostics Client](#sync-diagnostics-client). +- **The wait completes, but the data is still missing:** Check that the data was committed to the source database before you created the request, and that the user's Sync Streams include it. To see what the device has synced, use [PowerSync DevTools](/tools/devtools-overview) in your app. To see what the user's Sync Streams sync, use [Sync Test](#sync-test) or the [Sync Diagnostics Client](#sync-diagnostics-client). - **The wait fails or does not complete:** The wait has not confirmed catch-up. If it failed, check whether it was canceled or timed out. Check `SyncStatus` for connection, upload, or download errors, then check [replication lag](/maintenance-ops/replication-lag) and [instance logs](#instance-logs). ### Inspect Local SQLite Database Opening the SQLite file directly is useful for verifying sync state, inspecting raw table contents, and diagnosing unexpected data. See [Understanding the SQLite Database](/maintenance-ops/client-database-diagnostics) for platform-specific instructions (Android, iOS, Web), how to merge the WAL file, and how to analyze storage usage. -Our [Sync Diagnostics Client](/tools/diagnostics-client) and several of our [demo apps](/intro/examples) also contain a SQL console view to inspect the local database contents without pulling the file. Consider implementing similar functionality in your app. See a React example [here](https://github.com/powersync-ja/powersync-js/blob/main/tools/diagnostics-app/src/app/views/sql-console.tsx). +[PowerSync DevTools](/tools/devtools/using-devtools#data-inspector), our [Sync Diagnostics Client](/tools/diagnostics-client), and several of our [demo apps](/intro/examples) also contain a SQL console view to inspect the local database contents without pulling the file. Consider implementing similar functionality in your app. See a React example [here](https://github.com/powersync-ja/powersync-js/blob/main/tools/diagnostics-app/src/app/views/sql-console.tsx). ### Client-Side Logging @@ -165,7 +169,7 @@ Sync & API logs in the [PowerSync Dashboard](https://dashboard.powersync.com/) r #### Common Causes of Latency -- **Large initial sync**: if your Sync Streams result in a large dataset, the first sync after connecting will be slow. Inspect bucket sizes and sync state with the [Sync Diagnostics Client](/tools/diagnostics-client). +- **Large initial sync**: if your Sync Streams result in a large dataset, the first sync after connecting will be slow. Inspect bucket sizes and sync state with [Sync Test](#sync-test) if you're on PowerSync Cloud, or with the [Sync Diagnostics Client](/tools/diagnostics-client) if you self-host. - **Upload queue blocking downloads**: by default, uploads are processed before downloads, so a backlogged upload queue delays receiving new data. Buckets and streams at [priority 0](/sync/streams/prioritized-sync) are not blocked by uploads, but come with the trade-off of potential sync inconsistencies. - **Replication lag on the source database**: high write volume, long-running transactions, bulk updates, or backfills can cause replication to fall behind faster than the service can drain it. See [Replication Lag](/maintenance-ops/replication-lag) for source-specific causes and fixes. - **Too many buckets per user**: incremental sync overhead scales roughly linearly with the number of buckets per user. See [Too Many Buckets](#psync_s2305-too-many-buckets-/-parameter-query-results) above. diff --git a/images/usage/tools/dashboard-sync-test.png b/images/usage/tools/dashboard-sync-test.png new file mode 100644 index 000000000..822218fa6 Binary files /dev/null and b/images/usage/tools/dashboard-sync-test.png differ diff --git a/integrations/neon.mdx b/integrations/neon.mdx index 0927cb33c..537236804 100644 --- a/integrations/neon.mdx +++ b/integrations/neon.mdx @@ -303,14 +303,14 @@ The notes list is empty at first. Create a note, then disconnect your device fro ### Test Your Sync Streams (Optional) -To see which data syncs to a specific user, generate a development token for a user who signed up in the demo app, and open it in the [Sync Diagnostics Client](/tools/diagnostics-client). Use the user's ID as the token subject. This ID is the `owner_id` value of the user's notes. +To see which data syncs to a specific user, connect as a user who signed up in the demo app. Use the user's ID, which is the `owner_id` value of the user's notes. - In the PowerSync Dashboard, go to the **Sync Test** view. Enter the user ID as the token subject, then click **Generate token** and **Launch Sync Diagnostics Client**. + In the PowerSync Dashboard, go to the [Sync Test](/tools/powersync-dashboard#sync-test) view. Enter the user ID, then click **Connect**. - In the demo directory, run the following command and paste the token into the [Sync Diagnostics Client](https://diagnostics-app.powersync.com): + In the demo directory, run the following command to generate a development token for the user. Then paste the token into the [Sync Diagnostics Client](https://diagnostics-app.powersync.com): ```bash powersync generate token --subject= diff --git a/intro/setup-guide.mdx b/intro/setup-guide.mdx index ac81e0f16..afcb33fe5 100644 --- a/intro/setup-guide.mdx +++ b/intro/setup-guide.mdx @@ -617,7 +617,7 @@ For quick development and testing, you can generate a temporary development toke You'll use this token for two purposes: -- **Testing with the _Sync Diagnostics Client_** (in the next step) to verify your setup and Sync Streams +- **Testing with the _Sync Diagnostics Client_** (in the next step) to verify your setup and Sync Streams, if you self-host - **Connecting your app** (in a later step) to test the client SDK integration @@ -664,18 +664,18 @@ You'll use this token for two purposes: -## 6. [Optional] Test Sync with the Sync Diagnostics Client +## 6. [Optional] Test Sync -Before implementing the PowerSync Client SDK in your app, you can validate that syncing is working correctly using our [Sync Diagnostics Client](https://diagnostics-app.powersync.com) (this hosted version works with both PowerSync Cloud and self-hosted setups). - -Use the development token you generated in the [previous step](#5-generate-a-development-token) to connect and verify your setup: +Before implementing the PowerSync Client SDK in your app, you can validate that syncing is working correctly. If you're on PowerSync Cloud, use [Sync Test](/tools/powersync-dashboard#sync-test) in the PowerSync Dashboard. If you self-host, use our [Sync Diagnostics Client](https://diagnostics-app.powersync.com) with the development token you generated in the [previous step](#5-generate-a-development-token). - 1. Go to [https://diagnostics-app.powersync.com](https://diagnostics-app.powersync.com) - 2. Enter your development token at **PowerSync Token** (from the [Generate a Development Token](#5-generate-a-development-token) step above) - 3. Enter your PowerSync instance URL at **PowerSync Endpoint** (found in the [PowerSync Dashboard](https://dashboard.powersync.com/) - click **Connect** in the top bar) - 4. Click **Proceed** + 1. In the [PowerSync Dashboard](https://dashboard.powersync.com/), select your project and instance + 2. Go to the **Sync Test** view + 3. Enter a user ID + 4. Click **Connect** + + Sync Test connects a client in your browser as that user and shows [PowerSync DevTools](/tools/devtools-overview) for it. It needs the development tokens setting from the previous step. 1. Go to [https://diagnostics-app.powersync.com](https://diagnostics-app.powersync.com) @@ -689,12 +689,12 @@ Use the development token you generated in the [previous step](#5-generate-a-dev -The Sync Diagnostics Client will connect to your PowerSync Service instance and display [information](https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app#functionality) about the synced data, and allow you to [query](https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app#sql-console) the client-side SQLite database. +Both tools show the synced data and let you query the client-side SQLite database. The Sync Diagnostics Client shows this [information](https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app#functionality) and has a [SQL console](https://github.com/powersync-ja/powersync-js/tree/main/tools/diagnostics-app#sql-console). In Sync Test, use the DevTools **Data Inspector** tab. **Checkpoint:** - Inspect your synced tables in the Sync Diagnostics Client. These should match the Sync Streams you [defined previously](#4-define-sync-streams). This confirms your setup is working correctly before integrating the client SDK into your app. + Inspect your synced tables in Sync Test or the Sync Diagnostics Client. These should match the Sync Streams you [defined previously](#4-define-sync-streams). This confirms your setup is working correctly before integrating the client SDK into your app. ## 7. Use the Client SDK diff --git a/maintenance-ops/monitoring-and-alerting.mdx b/maintenance-ops/monitoring-and-alerting.mdx index df358f643..757044673 100644 --- a/maintenance-ops/monitoring-and-alerting.mdx +++ b/maintenance-ops/monitoring-and-alerting.mdx @@ -248,6 +248,17 @@ rid: Use the [Session Lifecycle](/debugging/log-reference#session-lifecycle) and [Session Fields](/debugging/log-reference#session-fields) reference to interpret the results. +### Sync As This User + +Use **Sync As This User** to reproduce what a user synced. It opens [Sync Test](/tools/powersync-dashboard#sync-test) as the user, with the connection parameters and Sync Stream subscriptions from their sync logs. Sync Test then shows the client in [PowerSync DevTools](/tools/devtools-overview). + +1. In the Sync & API logs, hover over an entry that has a user ID. +2. Click the **Sync As This User** button on the entry. If the **Metadata** display option is on, you can also open the menu of the `user_id` pill and choose **Sync As This User**. +3. Check the values in the dialog. If a value is wrong or missing, change it or add it. Sync logs keep only the first 20 connection parameters and shorten values longer than 100 characters, and the dialog notes the values that the logs could not fill in. To use the values from another recent Sync Session of the user, select them under the field. +4. Click **Sync As This User** to open Sync Test and connect. + +The button shows only if you can use Sync Test. See the [Sync Test requirements](/tools/powersync-dashboard#sync-test). + ### Replication Flush Entries To investigate replication throughput, select Replicator logs and search for `Flushed`. Each entry reports a batch of writes to bucket storage. See [Flushed Batches](/debugging/log-reference#flushed-batches) for message and field meanings. diff --git a/migration-guides/atlas-device-sync.mdx b/migration-guides/atlas-device-sync.mdx index a476e234c..4d62ac04d 100644 --- a/migration-guides/atlas-device-sync.mdx +++ b/migration-guides/atlas-device-sync.mdx @@ -87,7 +87,7 @@ Follow the steps for MongoDB and your client platform/framework in our standard - [Connect PowerSync To Your Source Database](/intro/setup-guide#3-connect-powersync-to-your-source-database) (MongoDB) - [Define Sync Streams](/intro/setup-guide#4-define-sync-streams) - [Generate a Development Token](/intro/setup-guide#5-generate-a-development-token) -- [Test Sync with the Sync Diagnostics Client](/intro/setup-guide#6-optional-test-sync-with-the-sync-diagnostics-client) +- [Test Sync](/intro/setup-guide#6-optional-test-sync) - [Use the Client SDK](/intro/setup-guide#7-use-the-client-sdk) - [Install the Client SDK](/intro/setup-guide#install-the-client-sdk) - [Define Your Client-Side Schema](/intro/setup-guide#define-your-client-side-schema) diff --git a/resources/usage-and-billing/usage-and-billing-faq.mdx b/resources/usage-and-billing/usage-and-billing-faq.mdx index 30541b201..df8051aaa 100644 --- a/resources/usage-and-billing/usage-and-billing-faq.mdx +++ b/resources/usage-and-billing/usage-and-billing-faq.mdx @@ -136,7 +136,7 @@ Narrow the results with structured filters: ![Instance logs filtered to show sync stream complete entries](/images/resources/instance-logs-sync-stream-complete.png) -You may need to scroll to load more logs. To get the filtered logs as a file, click the **Export** (download) button in the top-right of the logs toolbar. It exports the currently visible logs to CSV. +You may need to scroll to load more logs. To get the filtered logs as a file, click the **Export** (download) button on the right of the logs toolbar. It exports the currently visible logs to CSV. These log entries show which pattern below applies. If both the operation count and the transferred size are high, see [More Operations Than Rows](#more-operations-than-rows). If the operation count is moderate but the size is large, see [Large Rows](#large-rows). If the same user appears repeatedly in quick succession, see [Repetitive Syncing by the Same User](#repetitive-syncing-by-the-same-user). diff --git a/sync/advanced/reducing-bucket-count.mdx b/sync/advanced/reducing-bucket-count.mdx index 03792c63f..a07d0e0b8 100644 --- a/sync/advanced/reducing-bucket-count.mdx +++ b/sync/advanced/reducing-bucket-count.mdx @@ -51,9 +51,9 @@ New checkpoint: 800178 | write: null | buckets: 7 | param_results: 6 ["5#org_dat - `param_results` is the total number of parameter rows for this connection. - The array lists the bucket names. Each name already includes its parameter value. The list stops after 20 names. -### Sync Diagnostics Client +### Sync Test and the Sync Diagnostics Client -The [Sync Diagnostics Client](/tools/diagnostics-client) shows the buckets for one user. It does not load for a user who is over the limit, because that user's sync fails before the data loads. Use the instance logs and the error breakdown for those users. The client shows the bucket count, which may not be the limit you reached. Confirm the limit from the error message. +[Sync Test](/tools/powersync-dashboard#sync-test) on PowerSync Cloud and the [Sync Diagnostics Client](/tools/diagnostics-client) show the buckets for one user. Neither loads data for a user who is over the limit, because that user's sync fails before the data loads. Use the instance logs and the error breakdown for those users. Both tools show the bucket count, which may not be the limit you reached. Confirm the limit from the error message. diff --git a/sync/streams/quickstart.mdx b/sync/streams/quickstart.mdx index 475a59ac5..e9912faa5 100644 --- a/sync/streams/quickstart.mdx +++ b/sync/streams/quickstart.mdx @@ -257,7 +257,7 @@ const sub = await db.syncStream('todos', { list_id: 'abc' }) - **Primary Key**: PowerSync requires every synced table to have a primary key column named `id` of type `text`. If your backend uses a different column name or type, you'll need to map it. For MongoDB, collections use `_id` as the ID field; you must alias it in your stream queries (e.g. `SELECT *, _id as id FROM your_collection`). - **Case Sensitivity**: To avoid issues across different databases and platforms, use **lowercase identifiers** for all table and column names in your Sync Streams. If your backend uses mixed case, see [Case Sensitivity](/sync/advanced/case-sensitivity) for how to handle it. - **Bucket Limits**: Each user has a limit on how many buckets they can sync ([1,000 by default](/resources/performance-and-limits)), and the query pattern determines how many each stream creates. See [Bucket Count](/sync/streams/bucket-count) for how buckets are counted, and [Reducing Bucket Count](/sync/advanced/reducing-bucket-count) to resolve `PSYNC_S2305` errors. -- **Troubleshooting**: If data isn't syncing as expected, the [Sync Diagnostics Client](/tools/diagnostics-client) helps you inspect what's happening for a specific user. You can see which buckets the user has and what data is being synced. +- **Troubleshooting**: If data isn't syncing as expected, inspect what's happening for a specific user with [Sync Test](/tools/powersync-dashboard#sync-test) if you're on PowerSync Cloud, or the [Sync Diagnostics Client](/tools/diagnostics-client) if you self-host. You can see which buckets the user has and what data is being synced. ## Examples & Demos diff --git a/tools/devtools-overview.mdx b/tools/devtools-overview.mdx index 7dfee65b8..fc985cfb4 100644 --- a/tools/devtools-overview.mdx +++ b/tools/devtools-overview.mdx @@ -83,13 +83,18 @@ DevTools reads from the database that your app has open, so it shows the same da -## DevTools vs. Sync Diagnostics Client +## DevTools vs. Sync Test and the Sync Diagnostics Client -Use DevTools to inspect the client in your running app. Use the [Sync Diagnostics Client](/tools/diagnostics-client) to see the data that the Service syncs to a specific user. You can use both in tandem. +Use DevTools to inspect the client in your running app. To see the data that the Service syncs to a specific user without your app, connect a separate client as that user: -| | PowerSync DevTools | Sync Diagnostics Client | -| --- | --- | --- | -| **How it connects** | To your running app | With a user JWT and the PowerSync endpoint | -| **What you inspect** | Local SQLite data and sync state in your app | Sync data: buckets, operations, stream subscriptions | -| **Environment** | Development only | Any environment | -| **SDK-specific** | Yes | No. It works with all SDKs. | +- If you're on PowerSync Cloud, use [Sync Test](/tools/powersync-dashboard#sync-test) in the PowerSync Dashboard. It connects a client in your browser as the user and shows DevTools for that client. +- If you self-host, use the [Sync Diagnostics Client](/tools/diagnostics-client) with a [development token](/configuration/auth/development-tokens) for the user. + +Sync Test signs in with a development token that contains only the user ID. If your Sync Streams read other claims from the token, use the Sync Diagnostics Client with a token from your auth provider instead. + +| | PowerSync DevTools | Sync Test | Sync Diagnostics Client | +| --- | --- | --- | --- | +| **How it connects** | To your running app | As a user ID, from the PowerSync Dashboard | With a user JWT and the PowerSync endpoint | +| **What you inspect** | Local SQLite data and sync state in your app | The same DevTools panels, for a client in your browser | Sync data: buckets, operations, stream subscriptions | +| **Availability** | Development builds of your app | PowerSync Cloud | PowerSync Cloud and self-hosted | +| **SDK-specific** | Yes | No. It runs the Web SDK. | No. It works with all SDKs. | diff --git a/tools/overview.mdx b/tools/overview.mdx index 6852fd6bc..b635529f5 100644 --- a/tools/overview.mdx +++ b/tools/overview.mdx @@ -18,7 +18,7 @@ sidebarTitle: "Overview" - Web app to inspect and debug syncing. Works with both cloud and self-hosted PowerSync Service instances. + Web app to inspect and debug what a user syncs. Works with both cloud and self-hosted PowerSync Service instances. If you're on PowerSync Cloud, Sync Test in the dashboard does this without a separate app. diff --git a/tools/powersync-dashboard.mdx b/tools/powersync-dashboard.mdx index b77d9b1f5..4e206726c 100644 --- a/tools/powersync-dashboard.mdx +++ b/tools/powersync-dashboard.mdx @@ -70,7 +70,7 @@ When you navigate to a specific instance, you'll see a left sidebar with various - **Database Connection** - Configure the source database connection - **Client Auth** - Configure authentication settings - **Sync Streams / Sync Rules** - Edit, validate, and deploy your Sync Config. -- **Sync Test** - Test your Sync Streams +- **Sync Test** - Connect a client as any user and inspect what it syncs. See [Sync Test](#sync-test). - **Client SDK Setup** - Generate the [client-side schema](/intro/setup-guide#define-your-client-side-schema) based on your deployed [Sync Streams](/sync/streams/overview) - **Write API** - Resources for exposing the write API endpoint - **Logs** - View replication and service logs @@ -89,13 +89,44 @@ Here are some of the most common tasks you'll perform in the dashboard: - **Edit and deploy Sync Streams** - Select your project and instance and go to the **Sync Streams** view to edit your Sync Config, then click **"Validate"** and **"Deploy"** to deploy - **Generate development token** - Navigate to the **Client Auth** and ensure the **Development tokens** setting is checked. Click the "Connect" button in the top bar and follow instructions to generate a [development token](/configuration/auth/development-tokens). -- **Launch the Sync Diagnostics Client** - Navigate to the **Sync Test**, generate a development token and click "Launch" to launch the [Sync Diagnostics Client](/tools/diagnostics-client). +- **Test what a user syncs** - Navigate to the **Sync Test** view, enter a user ID, and click **Connect**. See [Sync Test](#sync-test). - **Copy your instance URL** - Click **Connect** in the top bar and copy the instance URL from the dialog. - **Generate client-side schema** - Click the **Connect** button in the top bar to generate the [client-side schema](/intro/setup-guide#define-your-client-side-schema) based on your deployed [Sync Streams](/sync/streams/overview) in your preferred language - **Monitor instance health** - Navigate to the **Health** view to see an overview of your instance status, source database connection, and recent deploys - **View logs** - Navigate to the **Logs** view to review replication and client sync logs - **Monitor metrics** - Navigate to the **Metrics** view to track usage metrics +### Sync Test + +Use the **Sync Test** view to check what your instance syncs to a specific user. It connects a client in your browser as that user and shows [PowerSync DevTools](/tools/devtools-overview) for that client. + +Before you start, check the following: + +- You have the **Development Tokens** permission. The Owner and Developer roles include it. See [Roles and Permissions](#roles-and-permissions). +- Development tokens are enabled in the **Client Auth** view. +- A Sync Config is deployed. + +To connect a client: + +1. Navigate to the **Sync Test** view. +2. Enter the user ID. Your Sync Streams read this value as `auth.user_id()`. +3. If your app passes [connection parameters](/sync/streams/parameters#connection-parameters) to `connect()`, add them. +4. Click **Connect**. + +To use the values that a user's app sent, open Sync Test from their sync logs with [Sync As This User](/maintenance-ops/monitoring-and-alerting#sync-as-this-user). + + + ![Sync Test view with a connected client and the PowerSync DevTools panel](/images/usage/tools/dashboard-sync-test.png) + + +The client stores the synced data in your browser. Connecting as a different user or to a different instance starts from an empty database, and signing out of the dashboard deletes the data. + +A connection that starts from an empty database downloads all of the user's data, like a new installation does. This counts toward your [data synced](/resources/usage-and-billing/pricing-example#data-synced) usage. + +The client signs in with a [development token](/configuration/auth/development-tokens), which contains only the user ID. If your Sync Streams read other claims from the token, the client can sync different data than the user's own devices. + +To connect your own app as this user, click **Generate Token** instead of **Connect** and copy the token. + ### Advanced: Service Version Locking Customers on our [Team and Enterprise plans](https://www.powersync.com/pricing) can lock their PowerSync Cloud instances to a specific version of the PowerSync Service. This option is available under your instance settings. @@ -143,17 +174,18 @@ The table below lists each permission, its available access levels, and what tho | --- | --- | --- | | Projects | View, Manage | View projects. Manage adds creating, renaming, and deleting projects. | | Instances | View, Deploy, Manage | View instances. Deploy adds deploying changes such as Sync Config and database connections. Manage adds creating and deleting instances. | -| Instance logs | View | View instance logs. | +| Instance Logs | View | View instance logs. | +| Development Tokens | Generate | Generate [development tokens](/configuration/auth/development-tokens) from Sync Test and the Connect button. A development token can sync as any user. | | Alert Rules | View, Manage | View Alert Rules. Manage adds creating, editing, and deleting them. | | Notification Rules | View, Manage | View Notification Rules. Manage adds creating, editing, deleting, and testing them. | | Private Endpoints | View, Manage | View Private Endpoints. Manage adds creating, editing, and deleting them. | | Team | View, Manage | View members. Manage adds inviting and removing members and changing their role assignments. | | Billing | View, Manage | View billing details and the current plan. Manage adds updating billing and changing the plan. | -| Organization settings | Manage | Update organization configuration, such as the organization name. | +| Organization Settings | Manage | Update organization configuration, such as the organization name. | -Not every permission offers all access levels. Each area shows only the levels that apply to it: Instance logs are read-only (View only), and Organization settings have no separate read-only view (Manage only). +Not every permission offers all access levels. Each area shows only the levels that apply to it: Instance Logs are read-only (View only), and Organization Settings have no separate read-only view (Manage only). -Some permissions depend on others, because access to the parent area is required to reach the child. Instances, Alert Rules, and Notification Rules require at least View on Projects, and Instance logs requires at least View on Instances. The builder adds the required parent permissions for you when you select a dependent one. +Some permissions depend on others, because access to the parent area is required to reach the child. Instances, Alert Rules, and Notification Rules require at least View on Projects. Instance Logs and Development Tokens require at least View on Instances. The builder adds the required parent permissions for you when you select a dependent one. ### Scoped permissions