> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kayanos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Profile, language, and signatures

> Manage your personal workspace preferences, interface language, notification settings, and signing credentials without weakening identity controls.

Your profile menu is the personal control point for how you use KayanOS. It provides access to profile/account settings, theme, notification preferences, language, signature management, and sign-out. These are personal controls, not a way to change another member’s role, bypass a service scope, or authorize an unsigned decision.

In the Citizen Services Directorate scenario, a Registry Officer uses Arabic for the interface, reviews notification preferences, and manages their own signing credentials only through the organization’s approved identity process. The service request `CSR-2026-00042` still carries the formal decision and evidence; the personal profile determines how the authorized member works with it.

## Goal

Select a usable language and interface direction, find the personal settings that affect daily work, understand the boundary between a preference and an organization-controlled setting, and use signature management safely when a formal workflow requires it.

## What the profile menu contains

The exact options can vary with deployment and permissions, but the profile menu is the route to these personal areas:

| Area                     | Use it for                                                                             | Do not use it for                                                                           |
| ------------------------ | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Profile/account settings | Reviewing and maintaining the current member’s account-level information where enabled | Changing another member’s organization role or business ownership                           |
| Theme                    | Choosing the interface appearance that is easiest for the member to use                | Changing an organization-wide design policy                                                 |
| Language                 | Switching the interface language for the current member                                | Translating record data or changing the language of a citizen-facing decision automatically |
| Notification preferences | Controlling eligible personal notification channels and preferences                    | Assuming an external channel is ready or an event was delivered                             |
| Signature management     | Listing and revoking the current member’s own signing credentials                      | Sharing credentials, enrolling another person, or bypassing a formal approval rule          |
| Sign out                 | Ending the current session                                                             | Removing the member from the organization                                                   |

## Change the interface language

The language selector currently offers English, Arabic, and Turkish. Changing language updates the local application preference and attempts to persist the current member’s preferred language for the active organization when that organization’s language configuration supports it. Arabic uses right-to-left interface direction.

To switch safely:

1. Open the profile menu.
2. Open **Language** and choose **Arabic**, **English**, or **Turkish**.
3. Allow the application to reload, then confirm that navigation, labels, and page direction are correct for the selected language.
4. Open a known request such as `CSR-2026-00042` and confirm that the team can still recognize the record’s fields, status, owner, and serial reference. A language preference changes interface labels, not the underlying field keys or record identity.
5. If you work in both English and Arabic, agree on stable operational references and status meanings so handoffs remain understandable across interfaces.

**Expected result:** the interface uses the selected language and Arabic screens render right-to-left, while access rules, entity keys, and service data remain unchanged.

## Use notification preferences deliberately

Open notification preferences when you need to control how you are alerted to assigned work. Available channels depend on organization setup and channel readiness. For example, an email channel needs a valid, non-suppressed email address; a push channel needs a registered device and permission; other optional channels can require a configured contact path and consent. The preference hierarchy is evaluated from the notification catalog through organization policy to the member setting.

Quiet-hours rules apply to external/non-in-app channels according to the configured policy; they do not delay the in-app notification stream. A preference is not proof that an external alert was delivered. For operationally important work, open Home, the task, or the related record and verify the current state.

For detailed daily use, see [Home and notifications](/work/home-and-notifications).

## Understand signature management and formal decisions

Signature management lets a member list and revoke their own signing credentials. It does not create a blanket right to sign any form or record. Whether a member can perform a formal signing action also depends on the configured workflow, the member’s signing capacity, relevant personal or position context, and the record/form permissions.

Use this safe sequence when your organization requires a signature:

1. Confirm that the service policy and configured form/action require a signature rather than a normal task completion or status update.
2. Confirm that you are the authorized member for the decision and that the correct personal or position-based signing capacity is in effect.
3. Open **Signature management** from the profile menu to review your own credential list. Do not expose private key material, enrollment codes, or another member’s credentials.
4. If a credential is no longer appropriate, revoke your own credential according to the organization’s identity process and notify the responsible administrator when required.
5. Return to the configured form or decision workflow and complete the signature only after reviewing the record, evidence, scope, and required data.
6. Verify that the workflow records the intended result. A task marked complete, a chat acknowledgment, or a profile setting is not a substitute for the signed outcome.

For configuration and member prerequisites, see [Member keys and signatures](/admin/member-keys-and-signatures) and [Form actions, logic, and signatures](/build/form-actions-logic-and-signatures).

## Availability and personal boundaries

Every signed-in member can use the profile menu, but a visible menu option does not expand operational authority. Language and theme are personal preferences. Notification channels require configured/eligible contact methods. Signature use requires the organization’s configured identity and formal workflow conditions. Managing a profile does not grant an ability to list, update, share, or approve a service record outside the member’s role and scope.

When something is missing, distinguish between:

* a personal setting that can be changed by the member;
* an organization policy or language/channel configuration that an administrator must maintain;
* a signing prerequisite that must be satisfied through the approved identity process; and
* a record/form permission that is separate from profile access.

## Safe testing

In an organization-approved non-production workspace, switch between English and Arabic and confirm both the page direction and a known service reference. Update an eligible notification preference and verify the in-app result without depending on an external channel. For signatures, use only an organization-approved training workflow with authorized test credentials; do not attempt to copy, share, export, or simulate another member’s identity.

## Troubleshooting

| Symptom                                           | What to check                                                                   | Safe response                                                                                     |
| ------------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Language changes back after reload                | Current organization’s language configuration and the member preference update  | Select the language again, then ask the organization administrator to verify the language setup   |
| Arabic layout looks unexpected                    | Browser/app reload and right-to-left rendering                                  | Reload after selection; report a specific screen and field label if direction remains incorrect   |
| An external notification does not arrive          | Channel eligibility, contact/consent, device permission, and quiet-hours policy | Check in-app notifications and the related work; do not treat a missed alert as a missed decision |
| A signing action is unavailable                   | Required form/action, signing capacity, credential state, and record scope      | Use the authorized decision path; do not replace it with a task checkbox                          |
| A credential should no longer be used             | Ownership, current credential list, and organizational identity procedure       | Revoke only your own credential and follow the approved escalation path                           |
| A member needs a different operational capability | Role verb and resource scope                                                    | Adjust the least-privilege role through administration, not personal profile settings             |

## Related guides

* Start work from [Home and notifications](/work/home-and-notifications).
* Learn formal decision controls in [Form actions, logic, and signatures](/build/form-actions-logic-and-signatures).
* Configure member signing prerequisites in [Member keys and signatures](/admin/member-keys-and-signatures).
* Review operational access in [Roles and access](/start/roles-and-access).

![KayanOS profile settings for a representative public-service staff member.](https://kayanos.app/docs-images/en/work/profile-language-and-signatures.png)