Documentation update ( Legal FAQ and more ) (#23266)
New legal section and minor fixes <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/twentyhq/twenty/pull/23266?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. -->
This commit is contained in:
@@ -162,6 +162,27 @@ Run `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = 'you@
|
||||
|
||||
In production, logic functions are disabled by default. Set the `LOGIC_FUNCTION_TYPE` environment variable to `LOCAL` or `LAMBDA` to enable them. This can be configured via environment variables or through the admin panel database variables. See the [Logic Functions setup guide](/developers/self-host/capabilities/setup#logic-functions-available-drivers) for details.
|
||||
|
||||
#### When I type a message in AI chat, it doesn't answer immediately and I must refresh the page to see the answer
|
||||
|
||||
Add following block to nginx config
|
||||
```
|
||||
location ~* ^/api/.*stream|\/graphql\/stream {
|
||||
proxy_pass http://twenty_backend;
|
||||
proxy_http_version 1.1;
|
||||
proxy_set_header Connection "";
|
||||
proxy_set_header Host $host;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
proxy_set_header X-Forwarded-Proto $scheme;
|
||||
proxy_buffering off;
|
||||
proxy_request_buffering off;
|
||||
proxy_cache off;
|
||||
gzip off;
|
||||
#chunked_transfer_encoding off;
|
||||
add_header X-Accel-Buffering no always;
|
||||
}
|
||||
```
|
||||
|
||||
### 1-click Docker compose
|
||||
|
||||
#### Unable to Log In
|
||||
|
||||
@@ -345,7 +345,7 @@
|
||||
"user-guide/settings/capabilities/profile-settings",
|
||||
"user-guide/settings/capabilities/experience-settings",
|
||||
"user-guide/settings/capabilities/domains-settings",
|
||||
"user-guide/settings/capabilities/updates-settings"
|
||||
"user-guide/settings/capabilities/community-settings"
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -354,6 +354,19 @@
|
||||
"pages": ["user-guide/settings/how-tos/settings-faq"]
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"key": "legal",
|
||||
"label": "Legal",
|
||||
"icon": "book",
|
||||
"pages": [
|
||||
"user-guide/legal/overview",
|
||||
{
|
||||
"key": "legalHowTos",
|
||||
"label": "How-Tos",
|
||||
"pages": ["user-guide/legal/how-tos/legal-faq"]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
},
|
||||
|
||||
@@ -337,6 +337,19 @@
|
||||
"pages": ["user-guide/settings/how-tos/settings-faq"]
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"key": "legal",
|
||||
"label": "Legal",
|
||||
"icon": "book",
|
||||
"pages": [
|
||||
"user-guide/legal/overview",
|
||||
{
|
||||
"key": "legalHowTos",
|
||||
"label": "How-Tos",
|
||||
"pages": ["user-guide/legal/how-tos/legal-faq"]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
},
|
||||
|
||||
@@ -145,6 +145,14 @@
|
||||
"label": "How-Tos"
|
||||
}
|
||||
}
|
||||
},
|
||||
"legal": {
|
||||
"label": "Legal",
|
||||
"groups": {
|
||||
"legalHowTos": {
|
||||
"label": "How-Tos"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@@ -55,7 +55,7 @@ This is on our roadmap.
|
||||
**Many to Many relations** are not yet available. For example, you cannot currently create a relation where:
|
||||
- Many People are linked to many Projects
|
||||
|
||||
<Note>Many to Many relations are planned for H1 2026.</Note>
|
||||
<Note>Many to Many relations are planned for H2 2026.</Note>
|
||||
|
||||
## Linking Records During Import
|
||||
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Export FAQ
|
||||
description: Frequently asked questions about exporting data.
|
||||
---
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Can we export all workspace data before cancellation, including custom objects, custom fields, relationships, notes, tasks, opportunities, attachments, workflows, permissions, and audit history?">
|
||||
Workspace data can be exported before cancellation with some exceptions: dashboards, workflows and permissions must be transferred manually and audit logs cannot be transferred.
|
||||
</Accordion>
|
||||
<Accordion title="Which elements cannot currently be exported or migrated?">
|
||||
Most elements can be exported or migrated with some exceptions:
|
||||
- workflows, dashboards and all settings (API keys, webhooks, audit logs, user settings, etc.) must be migrated manually
|
||||
- app-created objects and fields can be migrated by installing said app in different workspace, they shouldn't be migrated manually
|
||||
- some records, like workflow versions and workflow runs. are not transferable at all and are expected to be lost
|
||||
- some objects like message and calendar related objects shouldn't be exported as they're created when account is connected and synced periodically, they'll be synchronized again once you connect your account (as long as you have an access to said account, if it's an account of team member who left your company, then those messages must be exported, otherwise they'll be lost)
|
||||
</Accordion>
|
||||
<Accordion title="Is there an official cloud to self-hosted migration procedure or an assisted migration service?">
|
||||
As of now, there is no official cloud-to-self-hosted migration procedure. The general idea is to:
|
||||
- first, install apps to introduce app-owned objects and fields
|
||||
- replicate custom objects and fields added by users
|
||||
- use script with API keys or AI tools to migrate all data from one workspace to another
|
||||
- all non-transferrable objects must be migrated manually
|
||||
|
||||
Please be aware of a few things:
|
||||
- you can send up to 50 requests per minute on Pro plan or 100 requests per minute on Organization plan before hitting a request/min limit
|
||||
- each API request can have up to 200 records
|
||||
- some data in fields like Created by, Timeline activities and Updated by will be lost during import and overwritten by the system
|
||||
</Accordion>
|
||||
<Accordion title="Are exported files provided in open and documented formats?">
|
||||
Exported files in the UI are in Excel format, and all API requests can be saved in JSON format.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
@@ -60,7 +60,7 @@ Twenty supports various field types:
|
||||
To add a custom field to any object, follow these steps:
|
||||
1. Go to `Settings` in the left sidebar.
|
||||
2. Go to `Data Model`, then select the object you wish to customize.
|
||||
3. Proceed by clicking on `Add Field`.
|
||||
3. Proceed by clicking on `+ New Field`.
|
||||
4. Choose a field name and type that suits your requirements. Consider adding a field description for better understanding.
|
||||
|
||||
Your newly created field is now available within the application's fields. To display it on a specific view, click on the options menu, then select `Fields`.
|
||||
@@ -78,9 +78,7 @@ You can deactivate a field to hide it from the app without losing your data. Thi
|
||||
Here's how you can do it:
|
||||
|
||||
1. Find the field you want to deactivate in your object settings.
|
||||
|
||||
2. Click the three dots `⋮` next to the field to open the menu.
|
||||
|
||||
3. Select `Deactivate` from the dropdown.
|
||||
|
||||
<img src="/images/user-guide/fields/deactivate-field.png" style={{width:'100%'}}/>
|
||||
@@ -88,9 +86,7 @@ Here's how you can do it:
|
||||
What happens when you deactivate a field?
|
||||
|
||||
1. **In the app:** The field disappears and you can't add new values to it.
|
||||
|
||||
2. **Existing relationships:** If it's a relation field, existing connections stay but you can't create new ones.
|
||||
|
||||
2. **Existing relationships:** If it's a relation field, existing connections stay, but you can't create new ones.
|
||||
3. **API access:** You can still access the field and its data through the API.
|
||||
|
||||
You can reactivate Standard and Custom Fields or have the option to permanently delete them.
|
||||
|
||||
@@ -16,7 +16,7 @@ Standard objects are predefined entities in your workspace to help you get start
|
||||
|
||||
The `People` object stores your contacts. It includes contact details and interaction history, so you can see all your customer interactions in one place.
|
||||
|
||||
### Company
|
||||
### Companies
|
||||
|
||||
The `Companies` object stores your business accounts. It includes details like industry, size and location. Companies connect to both `People` and `Opportunities` objects.
|
||||
|
||||
@@ -48,8 +48,6 @@ To create a new custom object:
|
||||
<VimeoEmbed videoId="926288174" title="Video demonstration" />
|
||||
|
||||
3. Click on `+ New object` at the top. Enter the name (both singular and plural), choose an icon, and add a description for your custom object and hit Save (at the top right). Using Listing as an example of custom object, the singular would be "listing" and the plural would be "listings" along with a description like "Listings that hosts created to showcase their property."
|
||||
|
||||
|
||||
4. Your custom object is now created and will appear in your sidebar. You can start adding records to it right away.
|
||||
|
||||
## Managing Objects
|
||||
@@ -57,16 +55,18 @@ To create a new custom object:
|
||||
### Deactivating Objects
|
||||
If you don't need a standard or custom object:
|
||||
1. Go to Settings → Data Model
|
||||
2. Find the object you want to deactivate
|
||||
3. Click the toggle to deactivate it
|
||||
4. The object will be hidden from your workspace but data is preserved
|
||||
2. Find the object you want to deactivate and click it
|
||||
3. Go to object's **Settings** tab
|
||||
4. Click `Deactivate` button
|
||||
5. The object will be hidden from your workspace but data is preserved
|
||||
|
||||
### Reactivating Objects
|
||||
To bring back a deactivated object:
|
||||
1. Go to Settings → Data Model
|
||||
2. Look for deactivated objects (they'll be grayed out)
|
||||
3. Click the toggle to reactivate it
|
||||
4. The object and all its data will be restored
|
||||
2. Enable `Deactivated` filter
|
||||
3. Look for deactivated objects (they have `Deactivated` next to their name)
|
||||
4. Click `⋮` and then `Activate` to reactivate it
|
||||
5. The object and all its data will be restored
|
||||
|
||||
## Best Practices
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ Many-to-many relations use a **junction object** pattern: an intermediate object
|
||||
<img src="/images/user-guide/fields/junction-relation-diagram.png" style={{width:'100%'}}/>
|
||||
|
||||
<Warning>
|
||||
**Lab Feature**: Junction relations must be enabled at **Settings → Updates → Lab** before use.
|
||||
**Lab Feature**: Junction relations must be enabled at **Settings → Community → Features** before use.
|
||||
</Warning>
|
||||
|
||||
See [How to Create Many-to-Many Relations](/user-guide/data-model/how-tos/create-many-to-many-relations) for a complete step-by-step guide.
|
||||
@@ -51,7 +51,7 @@ See [How to Create Many-to-Many Relations](/user-guide/data-model/how-tos/create
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Select the object where you want to add the relation
|
||||
3. Click **+ Add Field**
|
||||
3. Click **+ New field**
|
||||
4. Select **Relation** as the field type
|
||||
5. Choose the target object(s) to relate to
|
||||
6. Configure the relation settings:
|
||||
|
||||
@@ -9,7 +9,7 @@ Custom fields let you capture information specific to your business. Add them to
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Select the object you want to add a field to
|
||||
3. Click **+ Add Field**
|
||||
3. Click **+ New Field**
|
||||
4. Choose a **field type** (see [Fields](/user-guide/data-model/capabilities/fields) for all types)
|
||||
5. Enter the **field name** and optional description
|
||||
6. Configure field-specific settings (see below)
|
||||
|
||||
@@ -12,7 +12,7 @@ Custom objects let you store information unique to your business that standard o
|
||||
## Steps
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Click **+ New object**
|
||||
2. Click **+ Add object**
|
||||
3. Fill in:
|
||||
- **Singular name** (e.g., "Listing")
|
||||
- **Plural name** (e.g., "Listings")
|
||||
@@ -27,7 +27,7 @@ Your object appears in the sidebar immediately.
|
||||
New objects start with basic fields. Add custom fields to capture the data you need:
|
||||
|
||||
1. In **Settings → Data Model**, select your object
|
||||
2. Click **+ Add Field**
|
||||
2. Click **+ New Field**
|
||||
3. Choose a field type, configure, and save
|
||||
|
||||
See [How to Create Custom Fields](/user-guide/data-model/how-tos/create-custom-fields) for details on field types and configuration.
|
||||
@@ -39,8 +39,8 @@ To link your object to People, Companies, or other objects, create a relation fi
|
||||
## Deactivating an Object
|
||||
|
||||
If you no longer need an object:
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Toggle the object off
|
||||
1. Go to **Settings → Data Model → object of choice → Settings**
|
||||
2. Click the **Deactivate** button
|
||||
|
||||
The object is hidden but data is preserved. You can reactivate or permanently delete later.
|
||||
|
||||
|
||||
+1
-1
@@ -50,7 +50,7 @@ When you enable the junction relation toggle, Twenty displays linked records dir
|
||||
First, create the intermediate object that will hold the connections.
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Click **+ New object**
|
||||
2. Click **+ Add object**
|
||||
3. Name it descriptively (e.g., "Project Assignment", "Team Member", "Product Order")
|
||||
4. Toggle "Skip creating a Name field" on
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ See [Relation Fields](/user-guide/data-model/capabilities/relation-fields) for r
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Select the object where you want the relation (typically the "many" side)
|
||||
3. Click **+ Add Field**
|
||||
3. Click **+ New Field**
|
||||
4. Select **Relation** as the field type
|
||||
5. Choose the **target object**
|
||||
6. Select **One-to-Many** or **Many-to-One**
|
||||
@@ -41,16 +41,26 @@ See [Relation Fields](/user-guide/data-model/capabilities/relation-fields) for r
|
||||
|
||||
Now each Person can be linked to a Company, and each Company shows its People.
|
||||
|
||||
## Deleting a Relation
|
||||
## Deactivating a Relation
|
||||
|
||||
1. Go to **Settings → Data Model**
|
||||
2. Find the relation field
|
||||
3. Click **⋮ → Deactivate**
|
||||
1. Go to **Settings → Data Model → object of choice**
|
||||
2. Find the relation field and click it
|
||||
3. Click **Deactivate** button
|
||||
|
||||
Links are preserved but hidden. Reactivate to restore.
|
||||
|
||||
<Note>
|
||||
**Deleting a relation doesn't delete records.** Only the link between them is removed.
|
||||
**Deactivating a relation doesn't delete records.** Only the link between them is removed.
|
||||
</Note>
|
||||
|
||||
## Deleting a Relation
|
||||
|
||||
1. Go to **Settings → Data Model → object of choice**
|
||||
2. Find the relation field and click it
|
||||
3. Click **Delete** button
|
||||
|
||||
<Note>
|
||||
Applies only to custom relations, standard relations can be only deactivated.
|
||||
</Note>
|
||||
|
||||
## Related
|
||||
|
||||
@@ -42,7 +42,6 @@ All active objects appear in the navigation. You can deactivate objects you don'
|
||||
No, field types cannot be changed after creation. If you need a different type, create a new field with the correct type, migrate your data, then deactivate the old field.
|
||||
</Accordion>
|
||||
|
||||
|
||||
<Accordion title="Why do I need different singular and plural names?">
|
||||
Our GraphQL API uses both forms for different operations:
|
||||
- `createPerson` (singular) for single record actions
|
||||
@@ -73,15 +72,15 @@ Currently, you cannot make custom fields required. All fields accept empty value
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Can I create formula fields?">
|
||||
Formula fields are coming in **Q1 2026**. In the meantime, you can use workflows to calculate and update field values automatically.
|
||||
Formula fields are coming in **H2 2026**. In the meantime, you can use workflows to calculate and update field values automatically.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Can I have nested fields in my objects?">
|
||||
Nested fields are coming in **Q1 2026**. Currently, you can use workflows to bring field values from related objects. For example, to display a company's industry on a Person record, create a custom field on People and use a workflow to synchronize the value.
|
||||
Nested fields are coming in **H2 2026**. Currently, you can use workflows to bring field values from related objects. For example, to display a company's industry on a Person record, create a custom field on People and use a workflow to synchronize the value.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Can I reorder fields in objects?">
|
||||
Field reordering will be available with custom layouts in **Q4 2025**. Currently, fields appear in alphabetical order.
|
||||
Yes, go to Settings → Data model → object of your choice → Layout and click **Customize record page**. If this button is disabled, you must create a record.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
@@ -93,7 +92,7 @@ Yes! Self-referencing relations are supported and recommended for use cases like
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Can I create many-to-many relationships?">
|
||||
Many-to-many relationships are coming in **H1 2026**. Currently, create an intermediate object with two one-to-many relationships as a workaround.
|
||||
Many-to-many relationships are coming in **H2 2026**. Currently, create an intermediate object with two one-to-many relationships as a workaround.
|
||||
|
||||
For example, to link People and Projects (many-to-many), create a "Project Assignments" object with:
|
||||
- A relation to People (many assignments → one person)
|
||||
@@ -147,6 +146,10 @@ Yes, you can import CSV data into any object, including custom objects. The impo
|
||||
<Accordion title="Can I export my data model configuration?">
|
||||
Currently, there's no built-in export for data model configuration. Contact support if you need to migrate your data model between workspaces.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="How many fields can a single object have?">
|
||||
The maximum number of fields a single object can have is 1600 fields as per Postgres limits, including both existing and deleted fields. Be aware that Twenty won't fix your workspace if limit of 1600 fields is reached as it falls under our Fair Usage policy.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Need More Help?
|
||||
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
title: Legal FAQ
|
||||
description: Frequently asked legal questions.
|
||||
---
|
||||
|
||||
## Data residency and international transfers
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="In which country and region would our workspace data, attachments, logs, and backups be stored?">
|
||||
Twenty Cloud runs on AWS servers located in Frankfurt, Germany.
|
||||
</Accordion>
|
||||
<Accordion title="Can the hosting region be contractually fixed for our workspace?">
|
||||
Hosting region can be selected starting 2027, alternatively you can reach out to [our Partners](https://twenty.com/partners/list?categories=HOSTING) to help you set up your instance.
|
||||
</Accordion>
|
||||
<Accordion title="Which sub-processors may process or access our CRM data, and in which countries are they located?">
|
||||
A list of all sub-processors is available in [our Trust center](https://trust.twenty.com/?tab=subprocessors).
|
||||
</Accordion>
|
||||
<Accordion title="What safeguards apply to international data transfers?">
|
||||
EU Standard Contractual Clauses with the UK Addendum and Swiss amendments apply to international data transfers within EU and all sub-processors.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Data Processing Agreement and legal roles
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Please provide the current Data Processing Agreement.">
|
||||
Latest DPA is available in your workspace at https://{your-domain}/settings/legal/dpa (e.g. https://getting-started.twenty.com/settings/legal/dpa).
|
||||
</Accordion>
|
||||
<Accordion title="Does Twenty act as the data processor for merchant and contact information stored in the CRM, while our company remains the data controller?">
|
||||
As per our [Privacy Policy](https://twenty.com/privacy-policy), Twenty acts as the data processor for merchant and contact information stored in the CRM, while your company remains the data controller.
|
||||
</Accordion>
|
||||
<Accordion title="Is CRM content ever used to train Twenty or third-party AI models?">
|
||||
CRM content is not used to train any AI model and Twenty does not have its own AI model, all AI models available on cloud are models provided by our sub-processors.
|
||||
</Accordion>
|
||||
<Accordion title="If optional AI processing exists, can it be fully disabled for our workspace?">
|
||||
AI can be turned off by disabling all AI models we offer in Settings → AI → Models, moreover no data is sent to AI if there is no interaction with AI chat and AI node in workflows.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Security and access controls
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Is encryption used in transit and at rest, what are your key-management practices, and how tenant data is isolated?">
|
||||
All data are encrypted in transit and at rest, all tenant data are isolated thanks to schema-per-tenant setup and our keys are periodically rotated.
|
||||
</Accordion>
|
||||
<Accordion title="Which Twenty personnel or sub-processors may access customer workspaces, for what purposes, and how is access approved and logged?">
|
||||
Twenty engineering and support team can access customer workspaces only upon customer's issue report and when customer agrees to allow access to workspace in Settings → General → Security.
|
||||
</Accordion>
|
||||
<Accordion title="What is your incident-notification process and target notification timeframe following a confirmed security incident affecting our data?">
|
||||
In the event of a confirmed personal data breach affecting your data, we will notify you without undue delay and in any event within 48 hours of becoming aware of it. Our notification will include, to the extent known at the time: the nature of the breach, the categories and approximate volume of data and individuals affected, likely consequences, and the remediation and mitigation measures taken or planned. We will provide updates as the investigation progresses.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Data retention and deletion
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="When an individual CRM record is deleted, when is it removed from active systems?">
|
||||
When a record is removed, first it's soft-deleted and still possible to restore, once it's permanently removed, it's removed from active systems.
|
||||
</Accordion>
|
||||
<Accordion title="How long may that record remain in backups or technical logs?">
|
||||
Removed record is in backup for 30 days, after that it's permanently removed.
|
||||
</Accordion>
|
||||
<Accordion title="When a workspace is closed or full deletion is requested, what exact timeline applies to production data, attachments, logs, and backups?">
|
||||
Removed workspace's data are immediately removed from active systems and backups of said workspace are available for 7 days, after 7 days, all data are permanently removed.
|
||||
</Accordion>
|
||||
<Accordion title="During any backup-retention period, is deleted data isolated from operational access and use?">
|
||||
Yes, during any backup-retention period, deleted data is isolated from operational use.
|
||||
</Accordion>
|
||||
<Accordion title="Are any categories of data retained longer for legal, billing, fraud-prevention, security, or audit purposes? If so, which categories and for how long?">
|
||||
For more info about data retention, you can request our Data Management and Retention Policy available in [our Trust Center](https://trust.twenty.com/?tab=documents).
|
||||
</Accordion>
|
||||
<Accordion title="Can Twenty provide written confirmation when a full deletion request has been completed?">
|
||||
We acknowledge erasure requests and provide written confirmation once deletion is complete.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Backups and resilience
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="What are the backup frequency and retention period?">
|
||||
Backups are created daily and retention period is 30 days.
|
||||
</Accordion>
|
||||
<Accordion title="What are the recovery-point objective and recovery-time objective for Twenty Cloud?">
|
||||
RTO and RPO are both 6 hours (as per our DPA).
|
||||
</Accordion>
|
||||
<Accordion title="What is the process for requesting or performing a restoration?">
|
||||
To request a restoration, please reach out to team via support chat or mail to [contact@twenty.com](mailto:contact@twenty.com).
|
||||
</Accordion>
|
||||
<Accordion title="Are backups encrypted and stored in the same region as the primary workspace data?">
|
||||
All backups are encrypted and stored in geographically separate locations within the same jurisdiction (e.g. within EU for EU data).
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Compliance
|
||||
<AccordionGroup>
|
||||
<Accordion title="Is Twenty GDPR compliant?">
|
||||
Yes, Twenty is [GDPR compliant](https://trust.twenty.com/?tab=securityControls&frameworks=gdpr_v1).
|
||||
</Accordion>
|
||||
<Accordion title="Is Twenty SOC 2 compliant?">
|
||||
Yes, Twenty is [SOC 2 compliant](https://trust.twenty.com/?tab=securityControls&frameworks=soc2_v1).
|
||||
</Accordion>
|
||||
<Accordion title="Is Twenty HIPAA compliant?">
|
||||
No, Twenty is in the process of becoming HIPAA compliant.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
If you have more questions, please check our [Terms and Conditions](https://twenty.com/terms), [Privacy Policy](https://twenty.com/privacy-policy) and [Trust Center](https://trust.twenty.com/), if your questions are still unanswered, send them to [contact@twenty.com](mailto:contact@twenty.com) or via support chat.
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
title: Legal
|
||||
description: Legal-related things
|
||||
---
|
||||
|
||||
Check our [FAQ](/user-guide/legal/how-tos/legal-faq).
|
||||
|
||||
## Useful links
|
||||
- [Terms and Conditions](https://twenty.com/terms)
|
||||
- [Privacy Policy](https://twenty.com/privacy-policy)
|
||||
- [Trust Center](https://trust.twenty.com/)
|
||||
@@ -3,7 +3,6 @@ title: Permissions
|
||||
description: Control access to objects, fields, and settings with role-based permissions.
|
||||
---
|
||||
|
||||
|
||||
Twenty's permission system allows you to control access to three main areas:
|
||||
- **Objects and Fields**: Control who can view, edit, or delete records and individual fields
|
||||
- **Settings**: Manage access to workspace configuration and administrative functions
|
||||
|
||||
+1
-5
@@ -24,10 +24,6 @@ Twenty supports SSO with:
|
||||
- Admin access to your identity provider
|
||||
- Admin access to Twenty workspace
|
||||
|
||||
<Note>
|
||||
**For self-hosting users willing to set up SSO**, reach out to contact@twenty.com
|
||||
</Note>
|
||||
|
||||
### Configuration Steps
|
||||
|
||||
#### 1. Access SSO Settings
|
||||
@@ -105,5 +101,5 @@ If you encounter issues, contact support with:
|
||||
- Configuration details (without sensitive data)
|
||||
|
||||
<Tip>
|
||||
Need SSO configured for your organization? [Find a certified Twenty partner](https://twenty.com/partners/list?categories=SOLUTIONING&ref=docs-sso) who specializes in SSO and identity setup. *(Prefer to loop in Twenty directly? [contact@twenty.com](mailto:contact@twenty.com).)*
|
||||
Need SSO configured for your organization? [Find a certified Twenty partner](https://twenty.com/partners/list?categories=SOLUTIONING&ref=docs-sso) who specializes in SSO and identity setup. *(Prefer to loop in Twenty directly? [contact@twenty.com](mailto:contact@twenty.com))*
|
||||
</Tip>
|
||||
|
||||
+7
-7
@@ -1,22 +1,22 @@
|
||||
---
|
||||
title: Updates Settings
|
||||
title: Community Settings
|
||||
description: Enable Early Access features in Twenty.
|
||||
---
|
||||
|
||||
## About Updates Settings
|
||||
## About Community Settings
|
||||
|
||||
The Updates section allows you to enable Early Access features before they're generally available.
|
||||
The Community section allows you to enable Early Access features before they're generally available as well as search for Twenty partners.
|
||||
|
||||
## Early Access Features
|
||||
|
||||
Early Access features are capabilities that are still being tested before general availability.
|
||||
|
||||
**Currently in Early Access:**
|
||||
- **Dashboards** — Visual reporting and analytics
|
||||
- **Junction relations** — Many-to-many relations
|
||||
|
||||
### How to Enable Early Access Features
|
||||
1. Go to **Settings → Updates**
|
||||
2. Navigate to the **Early Access** section
|
||||
1. Go to **Settings → Community**
|
||||
2. Navigate to the **Features** section
|
||||
3. Find the feature you want to enable
|
||||
4. Toggle it on
|
||||
5. The feature will be available immediately
|
||||
@@ -30,5 +30,5 @@ Early Access features may change based on user feedback. Your input helps us imp
|
||||
Your feedback helps improve Twenty:
|
||||
- Report issues with Early Access features
|
||||
- Share how you're using new features
|
||||
- Suggest improvements via the community Discord
|
||||
- Suggest improvements via the [community Discord](https://discord.gg/cx5n4Jzs57)
|
||||
|
||||
@@ -7,14 +7,13 @@ Domain settings live in three places, depending on what you're configuring.
|
||||
|
||||
## Workspace Domain
|
||||
|
||||
Configure under **Settings → General → Workspace Domain**.
|
||||
Configure under **Settings → General**.
|
||||
|
||||
Edit your subdomain name or set a custom domain for your workspace.
|
||||
|
||||
### Customize Domain
|
||||
1. Click **Customize Domain**
|
||||
2. Edit your subdomain (e.g., `yourcompany.twenty.com`)
|
||||
3. Or set up a custom domain (e.g., `crm.yourcompany.com`)
|
||||
1. Click **Subdomain** to edit your subdomain (e.g., `yourcompany.twenty.com`)
|
||||
2. Or click **Custom domain** to set up a custom domain (e.g., `crm.yourcompany.com`)
|
||||
|
||||
For custom domains, you'll need to configure DNS settings with your domain provider.
|
||||
|
||||
@@ -42,7 +41,7 @@ Configure under **Settings → Apps → your app → Settings → App URL**.
|
||||
Apps that expose routes on the web are served from a dedicated URL, shown in the **App URL** section. You can serve an app from a domain you own instead.
|
||||
|
||||
### Add Custom Domain
|
||||
1. Click **Add Custom Domain**
|
||||
1. Click **Custom Domain**
|
||||
2. Enter the domain you want to use (e.g., `app.yourcompany.com`)
|
||||
3. Configure DNS settings as instructed
|
||||
4. Verify the domain
|
||||
|
||||
@@ -8,7 +8,7 @@ Manage who has access to your workspace under **Settings → Members**.
|
||||
## Invite New Members
|
||||
|
||||
### Using Email Invitation
|
||||
1. Go to **Settings → Members**
|
||||
1. Go to **Settings → Members → Invite**
|
||||
2. Click **+ Invite**
|
||||
3. Enter the person's email address
|
||||
4. Select a role for the new member
|
||||
@@ -17,7 +17,7 @@ Manage who has access to your workspace under **Settings → Members**.
|
||||
The invited person will receive an email with a link to join your workspace.
|
||||
|
||||
### Using Invite Link
|
||||
1. Go to **Settings → Members**
|
||||
1. Go to **Settings → Members → Invite**
|
||||
2. Copy the workspace invite link
|
||||
3. Share the link with new team members
|
||||
4. They'll receive access once they sign up
|
||||
@@ -25,9 +25,9 @@ The invited person will receive an email with a link to join your workspace.
|
||||
## View and Manage Members
|
||||
|
||||
### View All Members
|
||||
Go to **Settings → Members** to see:
|
||||
- All active members
|
||||
- Pending invitations
|
||||
Go to **Settings → Members → Team** to see all active members
|
||||
|
||||
Go to **Settings → Members → Invite** to see pending invitations
|
||||
|
||||
### Edit a Member's Profile
|
||||
Click on a member to open their profile page. As an admin, you can:
|
||||
@@ -47,15 +47,15 @@ On the member's profile page:
|
||||
|
||||
### Remove a Member
|
||||
1. Click on the member to open their profile
|
||||
2. Click **Delete** to remove them from the workspace
|
||||
2. Click **Delete account** to remove them from the workspace
|
||||
|
||||
<Warning>
|
||||
Removed members lose access immediately. Their data (records, notes, tasks) remains in the workspace.
|
||||
</Warning>
|
||||
|
||||
<Warning>
|
||||
**Email sync is also removed.** If the deleted user was the only one who synced certain emails, those emails will be permanently removed from the workspace.
|
||||
</Warning>
|
||||
<Note>
|
||||
Emails and calendar events of deleted user are archived and available for other users.
|
||||
</Note>
|
||||
|
||||
## Pending Invitations
|
||||
|
||||
|
||||
@@ -3,7 +3,6 @@ title: Profile Settings
|
||||
description: Manage your personal profile and security settings.
|
||||
---
|
||||
|
||||
|
||||
## Personal Information
|
||||
|
||||
### Name and Email
|
||||
@@ -15,8 +14,8 @@ description: Manage your personal profile and security settings.
|
||||
|
||||
### Two-Factor Authentication (2FA)
|
||||
Enable 2FA to add an extra layer of security to your account:
|
||||
1. Go to **Settings → Profile Settings**
|
||||
2. Click **Enable 2FA**
|
||||
1. Go to **Settings → Profile**
|
||||
2. Click **Authenticator app**
|
||||
3. Scan the QR code with your authenticator app
|
||||
4. Enter the verification code to confirm
|
||||
|
||||
@@ -24,7 +23,6 @@ Enable 2FA to add an extra layer of security to your account:
|
||||
- **Change Password**: Update your current password
|
||||
- **Password Requirements**: Must be at least 8 characters long
|
||||
|
||||
|
||||
## Profile Management
|
||||
|
||||
### Delete Account
|
||||
@@ -33,7 +31,7 @@ Deleting your account will permanently remove your access to all workspaces. Thi
|
||||
</Warning>
|
||||
|
||||
To delete your account:
|
||||
1. Go to **Settings → Profile Settings**
|
||||
1. Go to **Settings → Profile**
|
||||
2. Scroll to **Danger Zone**
|
||||
3. Click **Delete Account**
|
||||
4. Confirm by typing your email address
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Workspace Settings
|
||||
description: Customize your workspace name and branding.
|
||||
---
|
||||
Those are accessible under **Settings → General**.
|
||||
|
||||
## Workspace Picture
|
||||
- **Upload Logo**: Add a custom workspace logo
|
||||
- **Supported formats**: PNG, JPEG, and GIF files under 10MB
|
||||
|
||||
@@ -154,7 +154,7 @@ You can configure approved access domains so team members with company email add
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="What are Early Access features?">
|
||||
Early Access features are capabilities being tested before general release. Currently, only **Dashboards** are in Early Access. They may change based on user feedback.
|
||||
Early Access features are capabilities being tested before general release. Currently, only **Junction relations** and **Calendar Day and Week Views** are in Early Access. They may change based on user feedback.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Are Early Access features safe to use?">
|
||||
@@ -162,9 +162,10 @@ Early Access features are functional but may change based on user feedback. They
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="How do I enable Early Access features?">
|
||||
1. Go to **Settings → Updates → Early Access**
|
||||
2. Find the feature you want
|
||||
3. Toggle it on
|
||||
4. The feature becomes available immediately
|
||||
1. Go to **Settings → Community**
|
||||
2. Scroll down to **Features** section
|
||||
3. Find the feature you want
|
||||
4. Toggle it on
|
||||
5. The feature becomes available immediately
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
@@ -12,11 +12,11 @@ Calendar view displays your records on a calendar based on a date field. Each re
|
||||
|
||||
1. Navigate to an object with date fields
|
||||
2. Click the view dropdown → **+ Add view**
|
||||
3. Name your view and click **Create**
|
||||
3. Name your view and click **Create**
|
||||
4. Open the **Options** on the right
|
||||
5. Select **Calendar** as the layout
|
||||
6. Choose the **date field** to use for positioning records
|
||||
5. Click **Update view**
|
||||
7. Click **Update view**
|
||||
|
||||
## Configuring the Calendar
|
||||
|
||||
|
||||
+1
-1
@@ -22,4 +22,4 @@ Get help from our core team with our 4-hour [Onboarding packs](https://twenty.co
|
||||
- **Data Migration**: Import existing data with proper workflow integration
|
||||
|
||||
### Implementation Partners
|
||||
Work with certified partners for advanced customizations. Contact us at contact@twenty.com to connect with our [implementation partners](https://twenty.com/partners).
|
||||
Work with certified partners for advanced customizations. Contact us at [contact@twenty.com](mailto:contact@twenty.com) to connect with our [implementation partners](https://twenty.com/partners).
|
||||
|
||||
Reference in New Issue
Block a user