If you need to manage space within your database, you can set a data compression policy. Currently we allow you to permanently delete versions in the collaboration log. Be aware that the current version of compression is a LOSSY process (data will be permanently deleted). Take that into consideration when configuring a policy.

The actual compression of data happens during the maintenance window. Please check with your system administrators to confirm when maintenance is scheduled.

Change Approval Enabled Tables

The number of versions is based on the major version and not the minor version. This means for a record on version 35.63 with a keep most recent 10 versions, it will keep all versions 26.0 +, rather than all versions 35.44+.

1. Overview

Data erasure allows you to permanently delete data in Cinchy. As the data owner, you can set an erasure policy on your table if you need to delete data for compliance reasons (Image 1).

The actual erasing of data happens during the maintenance window. Please check with your system administrators to confirm when maintenance is scheduled.

Once data is erased, any links pointing to erased data will look like this (Image 2):

2. Change Approval Enabled Tables

The time is counted based on the record's modified time stamp, not the deleted time stamp. This means for change approval records it is the time when the pending delete request was approved and moved to the Recycle Bin, not when the delete request was made.

1. Overview

Data Entitlements define who has access to do what on your Cinchy platform. These access controls are universally set at a cellular level, meaning that you can configure user access in the way that best supports your use case.

You can set entitlements such that specific users can view, edit, delete, insert, or all of the above for whichever data you want them to access.

Cinchy supports user-based, role-based, and attribute-based access controls.

1.1 User-Based Controls

User-based controls are entitlements given to specific users. This is done via the Users column.

Defining access based on a user means that even if the user changes their role, team, group, etc., they will still maintain their data entitlements.

1.2 Role-Based Controls

Role-based controls are entitlements given to set(s) or users based on their role in your environment. For example, you are able to define that only the Product team has access to insert records into a Product Roadmap table. Instead of configuring the entitlements user by user, which takes time and can lead to incorrect data when/if employees shift teams, you can configure it such that any user within the Product team automatically maintains the same level of control across the board.

In Cinchy, this is done via the Groups column.

1.3 Attribute-Based Controls

Attribute-based controls are entitlements given to a user(s) based on a defined set of "tags". This can include attributes such as their team, their role, their security clearance, their location, etc.

Defining entitlements based on attributes allows you to drill even deeper into the specificity of which users can do what on your tables.

In Cinchy, you can set up an infinite number of attributes based on your specific use case(s). This is done via Row Filters.

For example, if you have an Employee table that contains salary information visible only to certain people, you can configure a Row Filter such that the logged in user MUST have at least one of the following attributes to be able to see it:

• The user to whom the salary belongs

• Their manager

• All VPs

• The CEO

You are able to add as many attributes into your Row Filter as needed. For example you could only allow a user with the following set of tags to view a row: Located in Toronto, on the Marketing Team, and with a Security Clearance level of 2.

2. Changing Entitlements

1. When viewing a table, click on Data Controls > Entitlements from the left navigation menu (Image 1).

2. Currently both the table creator and anyone in the Cinchy Administrators group has access to perform any action on any objects. You can give granular entitlements at a Group or a User level, for both viewing and editing access (Image 2).

3. In the above scenario, John Smith is part of the Developers group. He is able to view all columns via the entitlement to the Developers group, and he is able to edit both the First Name and Last Name column through different entitlements.

3. Table Level Entitlements

There are certain entitlements in the Data Controls menu that apply to the entire table.

3.1 Marketplace

Approving this entitlement enables users to see and search for the table in the Marketplace/Homepage.

3.2 Bulk Export

Approving this entitlement enables users to export data from the table via the Manage Data screen (Image 3).

3.3 Direct Query

Approving this entitlement enables users to query the data from the table directly in the Query Builder (Image 4).

3.4 Design Table

Approving this entitlement enables users to alter the structure of the table.

3.5 Design Controls

Approving this entitlement enables users to change the permissions on a table.

4. Column Level Entitlements

There are certain entitlements in the Data Controls menu that apply only to columns.

4.1 View All Columns

Approving this entitlement enables users to view all columns within the table.

4.2 View Specific Columns

This is a drop down where you can select the specific columns you want to grant view access to for users.

4.3 Edit All Columns

Approving this entitlement enables users to edit all columns within the table.

4.4 Edit Specific Columns

This is a drop down where you can select the specific columns you want to grant edit access to for users.

4.5 Approve All Columns

Approving this entitlement enables users to approve all columns within the table. This also allows users to approve Create and Delete requests.

Approve permissions only apply when Change Approvals are enabled.

4.6 Approve Specific Columns

This is a drop down where you can select the specific columns you want to grant approve access to for users.

Approve permissions only apply when Change Approvals are enabled.

4.7 Link Columns

Link columns require both permission to the column within this table, as well as the column in the link column itself.

5. Row Level Entitlements

These are entitlements that apply to specific rows. Used in conjunction with Column Level entitlements this allows for granular cell level entitlements.

5.1 Insert Row

Approving this entitlement enables users to create new rows in the table.

5.2 Delete Row

Approving this entitlement enables users to delete rows in the table.

5.3 Viewable & Editable Row Filter

This is a CQL fragment that applies a filter to which rows will be viewable or editable. Think of the column entitlements and the fragment as a SQL statement applied to the table.SELECT {Edit Selected Columns} WHERE {Editable Row Filter}

5.4 Examples for Row Filter

Most of these examples will be with the editable row filter so it is easy to see the underlying data for comparison. However this can be done for viewable row data as well.

Sample Data

(Image 5)

Simple Example

With the following entitlements (Image 6):

• Edit Specific Columns: Age

• Editable Row Filter: [Age] > 30

Example with Viewable Data

(Image 7)

• View Specific Columns: First Name, Last Name

• Viewable Row Filter: [End Date] IS NULL OR [End Date] > GetDate()

Layer On Another Entitlement

(Image 8)

• View Specific Columns: All

• Edit Specific Columns: First Name, Last Name, Age

• Viewable Row Filter: [First Name] = 'John'

• Editable Row Filter: [First Name] = 'John'

Example for Current User

(Image 9)

For the All Users group:

(Image 10)

• View All Columns: Check

• Edit Selected Columns: First Name, Last Name

• Editable Row Filter: [User Account].[Cinchy Id] = CurrentUserId()

To allow a user to edit certain fields of their own data, you will need an association from a user to the [Cinchy].[Users] table. You can then use the following function to allow edit for that user, where [...] is the chain of link columns to get to the Users table.

[...].[Cinchy Id] = CurrentUserId()

You can find the Data Controls menu on the left-hand navigation bar of a table.

From here you may select to:

• Change your Data Entitlements

• Erase your Data

• Compress your Data