How an organization joins PULS
In PULS, an organization’s access to the modules goes through an approval process: the modules the organization wants to see are submitted to the PULS team, and the modules are enabled after the team’s approval. An organization can be opened in two ways.
| Path | Who starts it | Result |
|---|---|---|
| Registration and organization request | User | The organization is set up; the modules stay disabled until the PULS team approves. |
| The PULS team opening an organization | PULS team | The organization is opened and a 30-day trial period begins. |
Steps of registration and organization request
- 01The registration form is filled in: full name, job title, mobile phone, company name, company size, web address, email, and a password of at least 8 characters.
- 02When registration is complete, the email verification screen opens.
- 03The organization details are entered: organization name (at least 2 characters), organization ID (lowercase letters, digits, and hyphens only), time zone, and optionally the industry.
- 04The modules you want to see are selected; at least one module must be selected. This selection is not a purchase, it is a request.
- 05For the request to be evaluated, consent to being contacted is confirmed and the form is submitted with the «Set up and submit for approval» button.
- 06The organization is set up and the user who submitted the form becomes the organization’s owner (Organization Owner). At this stage no module is enabled in the organization; the user sees the approval waiting screen.
- 07The PULS team evaluates the request. All or some of the requested modules can be approved; the request can also be rejected. Approved modules are enabled for the organization and the user is notified by email.
Introduction with the sample company
A visitor who wants to see PULS in a company filled with data before setting up their own organization can request access to a guided tour prepared with the fictional data of a sample company. This request also goes through approval by the PULS team; if approved, the sign-in link is sent by email.
Trial period
An organization opened by the PULS team starts in the trial phase. The trial period is 30 days and is counted from the moment the organization is opened.
During the trial period, a banner showing the number of remaining days appears at the top of the application. The remaining days are counted as calendar days according to Istanbul time.
After the period ends, the organization is locked and access to the organization is closed. The organization’s data is not deleted; when a license is enabled, access is restored exactly as it was.
Roles
A user’s authority in the organization is determined by their role; a role is a set of permissions. PULS comes with system roles that are available in every organization. In addition to these, the organization can define its own roles.
| Role key | Name in the record | Coverage |
|---|---|---|
organization_owner | Organization Owner | Full access within the organization. |
organization_admin | Organization Admin | Administrator access within the organization. |
manager | Manager | Team management access. |
member | Member | Standard member access. |
viewer | Viewer | Read-only access. |
external_user | External User | Limited access for collaborators from outside the organization. |
The organization owner (organization_owner) and organization admin (organization_admin) roles see all modules that are enabled in the organization’s license. For the other roles, a separate view permission is required for each module.
Roles whose key begins with «platform_» belong to PULS’s own administration and cannot be assigned from within an organization.
The organization’s own roles
- The
member.update_rolepermission is required to define a new role. - When a role is created, the permissions are selected by marking them in the application’s permission list.
- System roles cannot be edited or deleted.
- The key of a role defined by the organization cannot begin with «platform_».
Inviting users
- The
member.invitepermission is required to send an invitation. By default, this permission is held by the Organization Owner and Organization Admin roles. - The role of the invited person is selected at the time of the invitation. Only system roles and the organization’s own roles can be selected.
- The invitation is sent by email; the invitation link is valid for 7 days.
- When an invitation is sent again to the same person from the same organization, the earlier pending invitation becomes invalid.
- An invitation can be accepted only by a user who is signed in with the email address to which the invitation was sent.
- When the invitation is accepted, the user becomes a member of the organization with the selected role.
Who sees a module
For a module to be visible to a user, two conditions must be met together:
- 01The module must be enabled in the organization’s license.
- 02The user’s role must be organization owner or organization admin, or the role must contain the module’s view permission.
The license condition is checked not only in the menu but also on the module’s own page: when the address of a module that does not appear in the menu is visited directly, the module page does not open either.
| Module | Product | View permission |
|---|---|---|
| Finance | PULS Finance Intelligence | finance.view |
| Sales | PULS Business Intelligence | sales.view |
| Stock | PULS Business Intelligence | stock.view |
| Human resources | PULS People Intelligence | hr.view |
| Sales OS (CRM) | PULS Sales Intelligence | crm.view |
| Purchasing | PULS Operations | purchasing.view |
| Logistics | PULS Operations | logistics.view |
| Problem & solution | PULS Operations | solution.view |
| Installed base | PULS Operations | installedbase.view |
| Production | PULS Manufacturing | manufacturing.view |
| Spare parts | PULS Operations | spares.view |
| Service and field | PULS Operations | service.view |
| PULS Connect | Shared foundation | integration.read |
Example of a sensitive permission: salary visibility
Some data is protected by a permission separate from the module permission. In the Human resources module, the gross and net salary fields depend on the hr.salary.view permission.
- Roles that carry this permission, together with the organization owner and organization admin, see the salary fields.
- For a user without this permission, the salary fields are not merely hidden on the screen; the server never sends these fields to the user’s browser.
- Operations that change salary data also require the same permission.
Language, currency, and number format
The interface language depends on the user; the currency and number format depend on the organization. Users working in different languages in the same organization see amounts in the same currency.
| Changeover | Bound to | Options | Default |
|---|---|---|---|
| Interface language | User | Türkçe, English, Deutsch | Türkçe |
| Currency | Organization | TRY, EUR, USD, GBP, CHF | TRY |
| Number format | Organization | tr-TR, de-DE, en-GB, en-US | tr-TR |
| Time zone | Organization | Entered when the organization details are filled in | The browser’s time zone |
The language is changed from the language selector in the top bar of the application; the selection is saved to the user’s profile.