Platform & Integrations Modules: Workflow and Permissions; API and Mobile Coming Soon

What does the platform and integrations category offer as shared infrastructure?

Platform and integrations modules cover not individual business processes but the shared functions all of them rely on: whose approval a request goes to, who can see which data, how users are notified of what, and how data leaves the system. Sora İK (Sora Yazılım Teknolojileri's human resources management software) builds this layer today with the following modules:

• Workflow & Approval Designer: to define approval steps and approvers for leave requests through a form, and to set a deputy who decides instead of the approver on requests attached to a workflow. A visual (drag-and-drop) design area and workflows for other requests such as expenses, advances or documents are coming soon.
• Roles, Permissions & Security: to set user roles and access rights, and to support account security with two-factor authentication (2FA) and an audit log.

"Integrations" in the category name refers to the planned ways for Sora İK to exchange data with external systems. Today, Sora İK has no ready-made connection to any software or institutional system; payroll, attendance ledger and report data can be exported as CSV. Open API & Webhooks, described below, for connecting with the company's own software, are coming soon. Our security approach is described on the Security and data protection page, and plans on the Pricing page.

Which layers do the platform modules coming soon sit in?

Modules coming soon fall into four groups: shared infrastructure that collects notifications in one place, an API and mobile app that will give access to Sora İK through different channels, an AI assistant that will help human resources (HR) users, and operational services that use data from several modules. Travel, meals and shuttle, and document generation sit in this category because they all rely on approval flows, permission definitions and notifications at the same time. Scope will be defined during development; all categories are listed on the Modules page.

Notification Center Coming soon

Notification Center is coming soon to collect the notifications produced by all Sora İK modules in one place and let each user choose how to receive them. Today, the business notifications Sora İK sends are limited to the leave process: emails go out for a new request, an approval, a rejection and the cancellation of approved leave. As modules multiply, if a request awaiting approval, a document about to expire, an upcoming training or a resolved request each arrives as a separate email, the important notification can get lost in the crowd. In the planned module, users will see their notifications in an in-app inbox; channels such as email and mobile push, and frequencies such as instant or daily digest, will be left to the user. Collecting pending approvals into a single digest for managers is also intended. Notifications will be triggered by the steps defined with the Workflow & Approval Designer. Personal data in notifications will be kept to a minimum; for example, instead of a pay amount or health information appearing in an email, the user will be directed to Sora İK. Preventing critical notifications, such as reminders of statutory deadlines, from being switched off entirely is also being evaluated.

Open API & Webhooks Coming soon

Open API & Webhooks is planned so that companies' own software can access Sora İK data in an authorized and limited way. An API (application programming interface) is a defined gateway that lets other software read data from or write data to Sora İK; a webhook sends a notice to an address the company sets when events occur, such as a new employee being added, a departure or a leave approval. Today, HR data mostly moves to other systems in manually prepared files that quickly go out of date. In the planned module, each access key will allow only specified data fields, the company administrator will create and revoke keys, and all access will be written to the audit log. The party building the connection will be the company's own software team or a provider the company authorizes; Sora İK has no ready-made connection to any particular software. When data is transferred to another system, the company remains the data controller. Accounting needs are addressed separately in the payroll and compensation category.

Mobile App Coming soon

The Mobile App will bring the most frequent Sora İK tasks to iOS and Android phones; it is among the modules coming soon. For employees who work in the field, in stores or on production lines and do not sit at a computer during the day, requesting leave, viewing a payslip or reaching a document may currently mean asking the HR team. The planned app will focus on bringing Employee & Manager Self-Service tasks, managers' pending approvals and notifications from the notification center to the phone. Recording the start and end of tasks for field staff will be handled together with the remote and field workforce work in the time and attendance category. Ending sessions remotely if a phone is lost, and following the web version's role and permission rules exactly, are among the core design principles. Which tasks the app will start with will be defined during development; publishing a mobile app also depends on the app stores' own review processes. The mobile app is intended as a channel alongside the web interface, not a replacement for it.

AI HR Assistant Coming soon

The AI HR Assistant is coming soon as an assistant to help HR specialists and managers with daily work. Planned uses include finding the right report for a question asked in natural language, drafting text for a job post or announcement and summarizing long records. The assistant will access only data the user is already authorized to see, with permissions coming from the Roles, Permissions & Security module. Every output it produces is a draft and a suggestion; there is no promise that it will be accurate, and it must be reviewed by the user. Decisions that affect individuals, such as hiring, promotion, pay or dismissal, will not be left to the assistant. Under KVKK (Türkiye's Personal Data Protection Law No. 6698), individuals may object to a result arising against them through the analysis of their data exclusively by automated systems; human approval is therefore a fixed part of the design. Which AI infrastructure will be used, where data will be processed and matters such as transfer abroad are planned to be explained on the Security and data protection page once settled.

Travel & Per Diem Coming soon

Travel & Per Diem is planned to bring the business trip process, from request to settlement on return, into one record. When approval comes by email, transport and accommodation details sit with different people and per diem is calculated in a spreadsheet afterwards, it is hard to trace which trip used which budget and who approved it. In the planned module, employees will open a request with the purpose, dates and route of the trip, approved through steps defined with the Workflow & Approval Designer. Per diem items such as daily allowance and accommodation will be calculated by the rules of the company's own travel policy; travel advances, closed against actual expenses on return, are also in scope. Different rules can be set for domestic and international travel, and managers will see their team's travel calendar and budget use in one view. Trip expenses will pass to the expense management work in the payroll and compensation category. The tax and social security treatment of per diem depends on legislation and the nature of the payment; we recommend setting policy rules with your accountant.

Meals, Shuttle & Vehicle Allocation Coming soon

Meals, Shuttle & Vehicle Allocation is being designed, and is coming soon, to run the day-to-day planning of the canteen, staff shuttle and company car services businesses provide, together with employee data. How many meals the canteen should prepare, which employee uses which shuttle route or which pool car is with whom on a given day is mostly tracked in separate lists, and leave and shift changes reach these lists late. In the planned module, the daily meal plan will be derived from the number of employees expected at the workplace, using approved leave and shift data. Shuttle routes, stops and passenger lists will be defined, and when an employee's shift changes, the related shuttle list will update too. Reservations are being considered for pool cars, and a link to the asset work in the employee management category for assigned cars. The aim is that details such as home addresses used in shuttle planning are seen only for this purpose and by authorized persons. The cost of these services as benefits, and their effect on payroll, are handled in the benefits work in the payroll category.

Document Generation Coming soon

Document Generation is planned to prepare documents employees frequently request from the company's own records and templates. Employment certificates, salary letters, payslips or statements of an employee's service periods at the company are mostly prepared by hand-copying details into a word processor template, which leads to typos and waiting. In the planned module, companies will define their own templates, with fields filled from Digital Employee Records and payroll records. Employees will send document requests through self-service; the prepared document will reach the employee after review by an authorized person, and a copy will be stored in Document & Contract Management. Numbering each document and recording when and by whom it was produced will help reduce the risk of altered documents. These are documents issued by the company; they do not replace documents obtained from institutions, such as the official service statement of the Social Security Institution (SGK). The company should check the adequacy of document content under legislation with its legal or HR advisor. Tracking document requests will be handled together with the employee requests work in the employee management category.