User Settings

What It Does

Mobile settings can render auth-specific blocks from @kit/auth/native/user inside @kit/settings pages:

• provider management (AuthProviderZone),
• active session controls (SessionZoneComponent),
• destructive account actions (DangerZoneComponent).

When To Use

• You want account/security controls inside settings.
• You want auth management UI driven by shared settings architecture.

Prerequisites

• settingsUI configured in apps/mobile/config/settings.ui.config.tsx.
• clientTrpc and authConfig available.

How To Use

Copy to Clipboardimport { AuthProviderZone, DangerZoneComponent, SessionZoneComponent } from '@kit/auth/native/user';

Expand
Copy to Clipboard{
  slug: 'security',
  title: 'Security',
  icon: 'Lock',
  settings: [
    {
      type: 'wrapper',
      settings: [
        {
          type: 'ui',
          render: <AuthProviderZone authConfig={authConfig} />,
        },
      ],
    },
    {
      type: 'wrapper',
      settings: [
        {
          type: 'ui',
          render: <SessionZoneComponent clientTrpc={clientTrpc} />,
        },
      ],
    },
  ],
},
{
  slug: 'index',
  settings: [
    {
      type: 'wrapper',
      settings: [
        {
          type: 'ui',
          render: <DangerZoneComponent className="max-w-4xl" clientTrpc={clientTrpc} />,
        },
      ],
    },
  ],
}
Expand

Filter API

Auth user settings in mobile rely on settings filters for page composition and auth package filters for translations.

MCP Context

Expand
Copy to Clipboardcapability: auth_mobile_settings_ui
entrypoints:
  - apps/mobile/config/settings.ui.config.tsx
  - apps/mobile/app/(app)/screens/settings-menu.tsx
  - apps/mobile/app/(app)/screens/settings/[...settings]/index.tsx
  - apps/mobile/hooks/use-filters.ts
  - apps/mobile/config/i18n.config.ts
  - kit/organization/src/native/filters/use-filters/use-settings-filters.tsx
  - kit/auth/src/native/filters/use-filters/use-translation-filters.tsx
inputs:
  - auth_config
  - client_trpc
outputs:
  - auth_management_sections_in_settings
constraints:
  - components must run under authenticated context
  - settings route params must match configured settings slugs
side_effects:
  - can terminate sessions or trigger account-destructive actions
Expand

Agent Recipe

1. Add auth UI zones to settingsUI page definitions.
2. Ensure clientTrpc and authConfig props are passed.
3. Verify settings menu routes to security and profile pages.

Troubleshooting

• If auth blocks do not render, verify they are wrapped in type: 'ui' settings nodes.
• If session actions fail, check TRPC client wiring in settings route.
• If navigation entry is missing, verify SettingsNavigation receives latest filtered UI config.

Related

• Settings
• Authentication