Settings, Security, and Support

Use settings to keep the workspace understandable and controlled. Financial data is sensitive, so access, exports, support access, API keys, and connected providers should be handled intentionally.

Settings areas

The settings sidebar includes:

• Financial connections > Sync: provider connection health and reconnect workflows.
• Account > Profile: personal details and preferences.
• Account > Security: password, passkeys, multi-factor authentication, connected sign-in accounts, and sessions.
• Account > Notifications: account, security, summary, and product update preferences.
• Organization > General: workspace details, slug, logo, SSO, business hours, support access, and danger zone.
• Organization > Members: members, invitations, roles, removals, and ownership transfer.
• Organization > Categories & tags: transaction categories, tags, and categorization rules.
• Organization > Billing: plan, billing email, billing address, invoices, and API usage.
• Organization > Developers: API keys, webhooks, and spreadsheet sync targets.
• Organization > Audit logs: available when your role and plan allow access.

Workspace roles

Workspace roles are Member and Admin. A workspace also has an Owner.

Members can use the workspace according to their access. Admins can manage more organization-level settings. Owners have the highest privileges and can transfer ownership. Owners cannot be removed until ownership is assigned to someone else.

Review members regularly from Settings > Organization > Members. Remove people who no longer need access and keep roles aligned with the work each person performs.

Invitations

Use invitations when adding someone to a workspace. Before inviting, decide whether they need to:

• View financial data.
• Manage sources.
• Edit categories and rules.
• Create spreadsheet sync targets.
• Use exports.
• Manage API keys or webhooks.
• Manage billing.
• Invite other members.

Only invite people who need access to the shared financial workspace.

Account security

Use Account > Security to manage your own sign-in security.

Available security surfaces include:

• Password changes.
• Passkey connection.
• Authenticator app multi-factor authentication.
• Active sessions.
• Connected sign-in accounts such as Google or Microsoft.

Review sessions if you used a shared device or no longer recognize a login. Disconnect sign-in methods you no longer use.

Organization SSO

Organizations can configure SSO when available. SSO settings control the protocol and whether users are forced to sign in through the configured provider.

Use forced SSO carefully. Make sure the right admins can still access the workspace before requiring it.

Financial source permissions

Only connect or import sources that should be available in the workspace. If a source should remain private, keep it in a separate organization or do not add it.

For shared households or teams, use clear account names and source labels so collaborators understand which records belong in each report.

Reconnect provider accounts when Tablewealth asks for fresh permissions. Google and Microsoft spreadsheet syncs also depend on the connected provider account having the right file access.

Spreadsheet permissions

Google Sheets sync uses the connected Google account to create and update Google workbooks. Microsoft 365 sync uses the connected Microsoft account to create and update Excel workbooks in OneDrive.

Anyone with access to the resulting spreadsheet may be able to see the financial data written there. Manage sharing in Google or Microsoft as carefully as you manage members in Tablewealth.

Google Sheets and Microsoft 365 syncs do not count against API usage. Local Excel sync requires Tablewealth access and counts against API usage.

API keys

Manage API keys from Settings > Organization > Developers.

API keys can have scopes such as:

• Organization: profile metadata.
• Accounts: account list and details.
• Transactions: transactions on allowed accounts.
• Holdings: holdings on allowed accounts.

API keys can apply to all accounts or selected accounts. Use the narrowest scope and account access that supports the integration.

Copy a new API key before closing the creation modal. Revoking a key stops it from working immediately, but its usage history remains.

API usage

API usage is visible in Settings > Organization > Billing and in the settings sidebar when usage is active.

Usage is measured in records for public API usage. Google Sheets and Microsoft 365 spreadsheet syncs do not count against API usage. Local Excel sync does count against API usage.

If usage is near the limit, review which integration is reading data and whether it can use narrower scopes, smaller date ranges, selected accounts, or less frequent refreshes.

Webhooks

Manage webhooks from Settings > Organization > Developers. Webhooks send events to your configured URL for supported triggers.

Keep webhook URLs controlled and use secrets where available. If an endpoint is no longer used, delete the webhook.

Privacy mode

Use Hide numbers in the sidebar when you need to share your screen or work in a public place. Privacy mode masks displayed financial values in supported product surfaces.

Privacy mode helps reduce accidental exposure, but it is not a permission boundary. People with workspace access can still access financial data through the app according to their role and available product surfaces.

Support access

Organization settings include Allow Tablewealth support access. Turn this on when you want Tablewealth support to view account details while helping with a support inquiry.

Leave support access off when you do not need active help. Do not send account credentials, raw access tokens, full account numbers, or unrelated financial records in support conversations.

Contacting support

When contacting support, include:

• Workspace name or slug.
• Source type: provider, manual, import, Google Sheets, Microsoft 365, local Excel, API, or webhook.
• Affected account, workbook, API key, or webhook when relevant.
• Date range.
• Last successful sync, import, or API request.
• What you expected to see.
• What you actually see.
• Screenshot with sensitive values hidden when needed.

Email help@tablewealth.com for local Excel sync access or product support that needs follow-up outside the app.