Manage contacts and address books
Find, review, create, and update contacts while respecting source ownership, consent, and personal-data handling rules.
Audience, roles, and scope
Workplace contacts and address-book interface; tenant directory administration and CRM workflows are out of scope.
Who this is for
- Workplace users with contact access
Roles
- Contact user
Before you begin
- Contact access
- A lawful, approved purpose for storing personal information
Article tags
- contacts
- address-book
- personal-data
- directory
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Create or update a contact
Use the correct address book and store only necessary data.
- 1Search before creating
Search by name and address to avoid duplicates and identify whether the existing record is editable.
- 2Review source and scope
Choose the intended address book and distinguish personal contacts from organization-managed directory records.
- 3Save minimal accurate data
Enter verified necessary fields, save, and reopen the contact to confirm the correct record changed.
The intended contact record contains accurate, necessary information without duplicating or overwriting a managed entry.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Do not copy directory or contact data into an unauthorized address book or export.
Known limitations
- Organization-directory records may be read-only or controlled by another source system.
- Synchronization, deduplication, and field persistence depend on connected services.
Troubleshooting
You cannot open Vianordis Workplace
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Contact search, detail, and editing surfaces were reviewed in source.
Reviewed paths at 5752ab1
src/app/contacts/page.tsxsrc/lib/contacts/api.tssrc/app/api/contacts/route.tssrc/app/api/contacts/addressbooks/route.ts
Contact support
Contact support when
- A repeatable Vianordis Workplace error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel