> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/objects/records/team-interactions-in-records.md).

# Team Interactions in Records

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

**Purpose:** Explains how user interactions create or update <code class="expression">space.vars.entity</code> associations and how those associations influence visibility and access across the platform.
{% endhint %}

## Overview

Team interactions are user-driven activities that establish or reinforce associations with a <code class="expression">space.vars.entity</code>. They signal participation and influence how visibility is evaluated under **My Associated Records** scope.

An interaction:

* Indicates engagement with a <code class="expression">space.vars.entity</code>
* Creates or reinforces an association
* Supports collaborative <code class="expression">space.vars.workflows</code>
* Intersects with permission evaluation

However, association and interaction are not identical:

* An interaction generates an association
* A user can be associated with a <code class="expression">space.vars.entity</code> without having interacted with it

Interactions operate within a layered visibility model that includes:

* Ownership
* Direct associations
* Relationship-based inheritance
* Permission Groups

Interactions contribute to association logic but do not override permission configuration.

***

## What Qualifies as an Interaction

An interaction is an action that meaningfully modifies, logs, or contributes to a <code class="expression">space.vars.entity</code>’s timeline history.

Examples include:

* Modifying a <code class="expression">space.vars.entity</code> (field updates, stage changes)
* Logging an <code class="expression">space.vars.activity</code>
* Adding notes or comments
* Starting an <code class="expression">space.vars.automation</code> from the <code class="expression">space.vars.entity</code> (when executed in user context)

Most interactions correspond to entries in the <code class="expression">space.vars.entity</code> <code class="expression">space.vars.timeline</code>.

{% hint style="info" %}
**Note:** Viewing a <code class="expression">space.vars.entity</code> does not create an association. Only user-driven interactions generate associations.
{% endhint %}

***

## How Associations Are Created

When a user interacts with a <code class="expression">space.vars.entity</code>, the platform may create or update an association between that user and the <code class="expression">space.vars.entity</code>. Associations fall into two categories:

### Direct Associations

Created when a user:

* Is assigned as the owner
* Is added through a team selector or user field
* Logs an activity tied to the <code class="expression">space.vars.entity</code>
* Modifies the <code class="expression">space.vars.entity</code>

Direct associations:

* Are stored on and editable from the <code class="expression">space.vars.entity</code>
* Are evaluated during permission checks

### Inherited Associations

Derived from relationships with other <code class="expression">space.vars.entities</code>. For example:

* An Agent associated with a Client
* A Policy related to a Client
* A Deal related to an Account

If a user is associated with a parent <code class="expression">space.vars.entity</code>, they may inherit association to related child <code class="expression">space.vars.entities</code> depending on relationship configuration and permission scope.

It's important to note that:

* Inherited associations cannot be edited from the child <code class="expression">space.vars.entity</code>
* They must be modified at the source (the related parent <code class="expression">space.vars.entity</code>)

#### Interaction Reinforcement & Role Visibility Within the Association

If a user is already associated with a <code class="expression">space.vars.entity</code>:

* Additional interactions reinforce participation history
* Duplicate associations are not created

Association alone does not guarantee visibility. Access still depends on:

* <code class="expression">space.vars.object</code>-level permissions
* &#x20;Whether the **My Associated Records** scope is enabled in the user’s Permission Group
* Field-level permissions
* Action permissions

Association qualifies a <code class="expression">space.vars.entity</code> for evaluation under **My Associated Records**. It does not independently grant access.

***

## Timeline Sharing and Relationship Effects

Relationships can extend visibility beyond a single <code class="expression">space.vars.entity</code>. When relationship configurations enable <code class="expression">space.vars.timeline</code> sharing:

* <code class="expression">space.vars.timeline</code> events from one related <code class="expression">space.vars.entity</code> may appear on another <code class="expression">space.vars.entity</code> when <code class="expression">space.vars.timeline</code> sharing is enabled
* These events may predate the child <code class="expression">space.vars.entity</code>’s creation

<code class="expression">space.vars.timeline</code> sharing is controlled by relationship configuration. <code class="expression">space.vars.activity</code> from one related <code class="expression">space.vars.entity</code> may appear on another <code class="expression">space.vars.entity</code>, even if it occurred earlier. This can influence how participation appears in reporting or portal contexts.

For relationship structure and inheritance configuration, see [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md).

***

## Agentic Workflows and Interaction Context

<code class="expression">space.vars.automations</code> run in a separate execution context.

Implications:

* <code class="expression">space.vars.automation</code>-triggered updates may create <code class="expression">space.vars.timeline</code> entries, but do not create user associations.

In most cases:

* Edit access is required to start an <code class="expression">space.vars.automation</code> on a <code class="expression">space.vars.entity</code>.
* Custom actions can grant limited permission to run specific <code class="expression">space.vars.automations</code>.

When designing visibility rules based on associations, consider how <code class="expression">space.vars.automations</code> may create, update, or modify <code class="expression">space.vars.entities</code> in ways that affect who can see them.&#x20;

For more information, see [Agentic Workflows](/docs/concepts/agentic-workflows.md).

***

## Important Considerations

When designing collaboration and access strategies:

* Interactions do not override Permission Groups.
* A user must have permission to access the <code class="expression">space.vars.object</code> itself (such as Clients, Deals, or Policies) and must also meet the <code class="expression">space.vars.entity</code>-level scope requirements (**All Records** or **My Associated Records**).
* Removing a direct association may remove visibility under **My Associated Records**.
* Inherited associations must be modified at their source relationship.
* Sharing team associations across related <code class="expression">space.vars.objects</code> can significantly expand who qualifies for visibility, making access behavior harder to predict.&#x20;
* Shared <code class="expression">space.vars.timeline</code> <code class="expression">space.vars.activity</code> can affect how past engagement appears.

Architectural clarity prevents unpredictable access behavior across UI, <code class="expression">space.vars.automation</code>, reporting, and API usage.

***

## What’s Next

Understanding Team Interactions ensures that administrators design predictable access strategies, architects model relationships responsibly, and developers anticipate visibility behavior when interacting with <code class="expression">space.vars.entities</code> programmatically.

To understand how interaction and association behavior surfaces in API responses or learn about <code class="expression">space.vars.entities</code> more generally, explore the topics below:

<details>

<summary>Related Topics</summary>

* [Records Core Concept](/docs/concepts/objects/records/records-core-concepts.md)
* [Records Data Model](/docs/concepts/objects/records/records-data-model.md)
* [Record Permissions](/docs/concepts/objects/records/record-permissions.md)
* [Record APIs](/docs/concepts/objects/records/records-apis.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/records/team-interactions-in-records.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.