What this chapter covers
This chapter describes the controls that work inside the application itself: how it is determined which organization a request belongs to, which operation requires which permission, license gates, API keys, webhooks, connection secrets, and audit logs. Topics relating to infrastructure and legal commitments are written on two public pages; they are not repeated here.
| Topic | Sheet |
|---|---|
| Data location | /guvenlik#veri-yeri |
| Encryption | /guvenlik#sifreleme |
| Retention and deletion | /guvenlik#saklama |
| Breach response | /guvenlik#ihlal |
| Exit and portability | /guvenlik#cikis |
| KVKK documents | /kvkk |
Separation of organizations from one another
Endpoints that take the organization information from the request read from the database whether the user has an active membership in that organization; if there is no membership, the request is rejected. If the membership cannot be read, the request still does not pass, and this is not reported to the user as «you are not a member».
- In operations that change or delete an existing record, the organization is read from the record itself, not from the request. For example, when an asset-assignment record is changed in the Human resources module, the record’s organization is first found, and then the user’s membership in that organization and write permission are checked.
- In requests that arrive with an API key, the organization is taken from the key’s own record.
- The check is also established at the database layer. For example, the audit log table returns only the rows of the organization of which the user is a member and for which they hold the
audit_log.readpermission.
Which operation requires which permission
Roles, the organization’s own roles, inviting users, and who sees a module are described in Chapter 1. The permissions required by the operations mentioned in this chapter are as follows:
| Leave | What it is needed for |
|---|---|
settings.read | Viewing the API Keys list |
settings.update | Creating and revoking API keys |
integration.read | Viewing the Webhooks list and the saved mappings |
integration.create | Creating a webhook |
integration.update | Editing and testing a webhook; viewing, testing, and saving the connections on the Direct SQL Connection screen; changing an existing mapping |
integration.delete | Deleting a webhook |
integration.import | Setting up a new mapping (integration.update is also sufficient) |
audit_log.read | Opening and exporting the Activity Log screen |
hr.salary.view | Viewing and changing salary fields |
License gates
Who a module is shown to in the menu and on the page is described in Chapter 1. The data endpoints of the Human resources, Finance, Sales OS (CRM), Sales, and Stock modules additionally pass through a common gate: the request of a signed-in user is checked before the endpoint itself runs. The module’s license must be enabled in the organization, and the user must be the organization owner or organization admin, or the module’s view permission must be present in the user’s role.
- This gate is at the module level. Field-level checks such as salary are performed separately inside the endpoint.
- If the gate cannot read the permission information, the request does not pass; the response is not «you are not authorized» but that the permission information could not be read.
- The PULS Connect endpoints (file upload, mapping, transfer, automatic fetch, report reconciliation, direct SQL connection, API keys, webhooks and sending data via the API) check the PULS Connect license themselves. If there is no license, the response says that this section is not in the company’s package.
- When the address of the PULS Connect screens is opened without a license, you are redirected to the organization’s package page.
Salary visibility
The gross and net salary fields depend on the hr.salary.view permission; details are explained in Chapter 1. This check is performed inside the Human Resources endpoints: salary fields are removed from the records returned to a user without the permission, and a request that changes a salary is rejected. Therefore the result is the same even if the endpoint is called directly from outside the screen.
API keys
An API key lets other software access PULS on behalf of your organization. The screen is reached from the «Other ways to connect» strip of the Data sources screen or from the command palette. The list is viewed by those with the settings.read permission; creating and revoking keys is done by those with the settings.update permission.
- 01In the «Key name» field you write what the key will be used for.
- 02For «Expiration date» you choose 30 days, 90 days, 180 days or 1 year; if left blank, the key has no expiry.
- 03Under «What should this key be able to do?» you select at least one permission. A permission name that is not recognized is rejected.
- 04An additional permission that depends on a permission (for example, sending employee data) can be granted only by a user who holds that permission in their own role.
- The full key is shown only once, at the moment it is created. PULS stores not the key itself but its digest and its first 12 characters.
- For each key, the list shows its name, its first characters, the names of the permissions granted, its expiration date or the «No expiry» label, and the date it was last used.
- A request made with a key that has been revoked, has expired, or belongs to an archived organization is rejected.
- Creating and revoking a key are written to the activity log.
| Permission | Name on the screen |
|---|---|
data.write | Send data to PULS |
stock.view | Send stock data (additional permission) |
hr.view | Send employee data (additional permission) |
purchasing.manage | Send purchase orders (additional permission) |
notifications.write | Send notifications |
org.read | Read company information |
members.read | Read user list |
features.read | Read package information |
files.read | Read file list |
audit_logs.read | Read activity logs |
Webhooks
A webhook is PULS sending a notification to an address you specify when an event occurs in your organization. On the screen you can create, test, disable and delete webhooks.
- Addresses that point to an internal or private network are rejected when created; the address is checked again before every delivery and redirects are not followed.
- The signing key is shown only once, at the moment it is created; the list does not return it.
- Every delivery is signed with this key using HMAC-SHA256. The signature arrives in the
X-PULS-Signatureheader with thesha256=prefix, and the name of the event arrives in theX-PULS-Eventheader. - Creating and deleting a webhook are written to the activity log.
Events you can subscribe to: hr_employee.created, hr_employee.updated, hr_employee.deleted, file.uploaded, file.deleted, member.invited, member.joined, member.removed, subscription.created, subscription.updated, subscription.cancelled. The body of some events carries personal data; for example, employee events send the employee’s name, and the invitation event sends the invited e-mail address. Choose the address with this in mind.
Connection passwords and addresses
- The database password entered on the Direct SQL Connection screen is encrypted when saved. If encryption cannot be performed, the connection is not saved; the password is not stored as plain text.
- When saved connections are listed, the password is never sent back in any form. If you leave the password field empty when editing, the old password is kept.
- Testing a connection saves nothing.
- The addresses entered on the Automatic fetch screen are also stored encrypted and are not sent back to the screen.
Activity log
This screen lists who did what in your organization. It is opened from the command palette or the mobile settings menu. For a user who does not have the audit_log.read permission and is not an organization owner or organization administrator, the page behaves as if it does not exist.
| Column | What it shows |
|---|---|
| Action | The code of the action performed, for example member.invite or webhook.create (underscores are shown as spaces) |
| User | The name of the user who performed the action; the e-mail address if there is no name |
| Target | The type of the record the action was performed on |
| IP | The application does not fill this field; «—» is shown |
| Date | The time of the action |
- Records are shown 50 rows per page, starting with the most recent; if there are several pages, you move through them with «Previous» and «Next». The heading states the total number of records. On narrow screens, the User, Target and IP columns are hidden.
- «Download CSV» exports all records: record ID, action, target type and ID, user ID and time.
- If there are no records yet, the screen says so.
Personal data when ingesting data
- On the Mapping screen, a field that carries personal data cannot be saved unless «KVKK approval» is checked; the server also rejects a personal field without approval.
- On the Automatic fetch screen, personal fields are not pre-filled and are marked as «personal».
- The ready-made query templates of the PULS bridge do not include the Turkish national ID number (T.C. kimlik numarası); the staff template also leaves out the salary, address, date of birth, e-mail and telephone fields.
- On the Report Reconciliation screen, the selected report file is read in the browser; only totals are sent to PULS and the result is not saved.
KVKK documents and rights
PULS appears in two separate roles. It is the data controller for the data of its own site visitors, of those who fill in request forms, and of account holders. For the employee, customer and supplier data that an organization transfers to PULS, however, the data controller is that organization and PULS is the data processor. Therefore an employee of an organization submits requests concerning their own data to the organization they work for.
| Document | Address | Status |
|---|---|---|
| Privacy notice | /kvkk/aydinlatma | In force |
| Cookie policy | /kvkk/cerez | In force |
| Sub-processors | /kvkk/alt-isleyenler | In force |
| Data inventory | /kvkk/veri-envanteri | In force |
| Data Processing Agreement | /kvkk/veri-isleme-sozlesmesi | Draft |
- All of the documents are listed on the
/kvkkpage. A document in draft status is shown with a banner at the very top of its page stating that it is not in force. - The rights of data subjects and the way to apply are written in the «Your rights (KVKK Art. 11)» section of the
/kvkk/aydinlatmapage.