# Contact Permissions

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Explains how <code class="expression">space.vars.contact</code> permissions work in <code class="expression">space.vars.Kizen\_company\_name</code>, how they align with <code class="expression">space.vars.object</code> permissions, and how they control access to creating, editing, viewing, and performing bulk actions on <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>.
{% endhint %}

## Overview

<code class="expression">space.vars.contacts</code> are a special type of <code class="expression">space.vars.object</code> used to represent people in the platform. <code class="expression">space.vars.contact</code> permissions determine:

* Whether a user can see <code class="expression">space.vars.contacts</code> across the platform
* Whether a user can create, edit, archive, or export <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>
* Whether a user can perform single or bulk actions on <code class="expression">space.vars.contacts</code>
* How <code class="expression">space.vars.contact</code> access is enforced across the UI, APIs, <code class="expression">space.vars.automations</code>, integrations, and exports

### How Contact Permissions Work

<code class="expression">space.vars.contact</code> permissions follow the same two-level permission model as other <code class="expression">space.vars.objects</code>, with additional system-level behavior specific to people, communication, and identity.

Permissions are configured through Teams, Roles, and Permission Groups and govern <code class="expression">space.vars.contact</code> visibility, record access, and actions such as creating, editing, archiving, uploading, and exporting. In addition, <code class="expression">space.vars.contacts</code> include <code class="expression">space.vars.contact</code> field permissions, which control whether users can edit <code class="expression">space.vars.contact</code>-specific fields and settings that do not apply to <code class="expression">space.vars.objects</code>.

For full details and examples, see [Object Permissions.](/docs/concepts/objects/object-configuration/object-permissions.md)

***

## Contact-Specific Permission Areas

<code class="expression">space.vars.contacts</code> represent people, so their permissions include additional controls for communication, subscriptions, and identity-related actions.

### Accessing Contact Permission Settings

{% stepper %}
{% step %}

#### Go to Contacts and select **Object Settings** from gear icon

<div data-with-frame="true"><figure><img src="/files/ZnGk7SEp1fekOkDqze6c" alt="" width="223"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select the Permissions tab (Step 5 in Object Configuration)

<div data-with-frame="true"><figure><img src="/files/aWf9NGsB1nTueYRMCkMe" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

The Permissions step contains all available <code class="expression">space.vars.contact</code> permission settings.

<div data-with-frame="true"><figure><img src="/files/WVtIArq5eQT8gaVPI0n0" alt="" width="563"><figcaption></figcaption></figure></div>

All permissions discussed below can be located from this page.

### Single-Record Contact Actions

<code class="expression">space.vars.contacts</code> include permissions that allow users to perform communication and interaction actions on individual <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>.

<div data-with-frame="true"><figure><img src="/files/8Cb4GxRIHcZQS5qB212V" alt="" width="563"><figcaption></figcaption></figure></div>

Under **Perform Single Record Actions**, <code class="expression">space.vars.contact</code>-specific permissions include:

* **Send Single Message:** Allows sending an email or text message from an individual <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>
* **Modify Agentic Workflow:** Allows starting, pausing, or cancelling <code class="expression">space.vars.automations</code> from the <code class="expression">space.vars.contact</code> context
* **Team Associations:** Controls access to employee-based associations for <code class="expression">space.vars.contacts</code>
* **Subscription Lists:** Allows viewing and managing a <code class="expression">space.vars.contact</code>’s email subscription status, including opt-in and unsubscribe state
* **View Timeline:** Allows viewing message history and interaction activity for a <code class="expression">space.vars.contact</code>

These actions do not exist for standard <code class="expression">space.vars.objects</code> because they depend on a Contact’s identity and system-managed communication status.

Having permission to edit a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> does not guarantee that communication actions are available. Actions may still be restricted based on system-managed <code class="expression">space.vars.contact</code> state, such as email status, suppression, or integration configuration.

### Contact-Specific Bulk Actions

<code class="expression">space.vars.contacts</code> also introduce bulk permissions for communication and subscription workflows that are not available on other <code class="expression">space.vars.objects</code>. These permissions control whether users can perform communication or subscription-related actions across multiple <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> at once.

<div data-with-frame="true"><figure><img src="/files/TLuNeK5KSYQH8SETQRJM" alt="" width="563"><figcaption></figcaption></figure></div>

Under **Perform Bulk Actions**, <code class="expression">space.vars.contact</code>-only permissions include:

* **Send Email:** Allows users to send emails to one or more <code class="expression">space.vars.contacts</code>, subject to email status, suppression rules, and permission checks
* **Send Text:** Allows users to send text messages to one or more <code class="expression">space.vars.contacts</code> when SMS is configured and the <code class="expression">space.vars.contact</code> has a valid mobile number
* **Send Survey:** Allows users to send surveys to <code class="expression">space.vars.contacts</code> as part of bulk communication workflows
* **Change Tags:** Allows users to add or remove tags on one or more <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> for categorization and segmentation
* **Manage Subscription:** Allows users to view and update <code class="expression">space.vars.contact</code> email subscription status, subject to system-managed compliance rules

Unlike generic bulk actions (such as changing field values or exporting <code class="expression">space.vars.entities</code>), these actions are explicitly tied to <code class="expression">space.vars.contacts</code> and reflect workflows that apply only to people.

Bulk communication actions are still subject to:

* <code class="expression">space.vars.entity</code>-level permissions
* Field-level access
* System-managed <code class="expression">space.vars.contact</code> state (such as opt-in status or suppression)

### Identity and Communication Field Permissions

<code class="expression">space.vars.contacts</code> expose field-level permissions that directly affect identity and contactability.

<div data-with-frame="true"><figure><img src="/files/wHZBtUBKkjc8WANKbtl1" alt="" width="563"><figcaption></figcaption></figure></div>

When you scroll down further on the page, under **Individual Contact Field Permission (Set All)**, permission controls include:

* **Email:** The primary identifier for a <code class="expression">space.vars.contact</code>, used to determine email contactability and enable email-based communication and <code class="expression">space.vars.automations</code>
* **Email Status:** A system-managed field that reflects a <code class="expression">space.vars.contact</code>’s email opt-in and deliverability state and may block email sending regardless of user permissions
* **Mobile Phone:** Determines SMS contactability and enables text messaging and SMS-based <code class="expression">space.vars.automations</code> when configured
* **Tags:** A <code class="expression">space.vars.contact</code>-specific, dynamic field used for categorization, segmentation, and triggering <code class="expression">space.vars.automations</code> and bulk actions
* **Timezone:** Stores a <code class="expression">space.vars.contact</code>'s local time zone and may be used to schedule or personalize communication timing
* **Birthday:** A date field used for personalization and date-based <code class="expression">space.vars.automations</code> and segmentation

These fields differ from typical <code class="expression">space.vars.object</code> fields because they:

* Determine whether communication actions are allowed
* Are referenced by campaigns and <code class="expression">space.vars.automations</code>
* May be partially system-managed (for example, Email Status)

***

## Contact Permissions in API Responses

Permissions for <code class="expression">space.vars.contacts</code> are surfaced directly in API responses, just like other <code class="expression">space.vars.objects</code>. For more information, see [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md).

{% hint style="warning" %}
**Caution**: <code class="expression">space.vars.contact</code> API responses indicate whether the current user can access, edit, create, or perform bulk actions on <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>. <code class="expression">space.vars.contact</code>-specific communication actions may still be restricted by system-managed <code class="expression">space.vars.contact</code> state (such as email status or suppression), even when these permissions are present.
{% endhint %}

***

## Important Considerations

When working with <code class="expression">space.vars.contact</code> permissions, keep the following in mind:

* Contacts follow the same permission model as <code class="expression">space.vars.objects</code>, but support additional system behavior
* Platform-level <code class="expression">space.vars.contact</code> access does not imply <code class="expression">space.vars.entity</code>-level access
* Missing <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> or fields often indicate permission restrictions, not missing data
* Bulk <code class="expression">space.vars.contact</code> actions are subject to the same <code class="expression">space.vars.entity</code>-level permission checks
* Permission misconfiguration is a common source of <code class="expression">space.vars.contact</code>-related issues in both UI and API workflows

***

## What’s Next

From here, you may want to explore other topics related to <code class="expression">space.vars.contact</code> Permissions below:

<details>

<summary>Related Topics</summary>

* [Permissions](/docs/settings-and-administration/permissions.md)
* [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md)
* [Contacts](/docs/concepts/objects/contacts.md)
* [Custom Fields](broken://pages/6rrJeEIzfjMAZY62pfmc)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/objects/contacts/contact-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.