Security & infrastructure
CloudotNet's approach to security rests on separating every company's data in the database itself, letting people see only the records they're authorized for, and keeping the work done on tasks traceable. This page explains, in plain language, the details your technical team may ask about.
CloudotNet serves many companies from the same infrastructure, but their data never mixes. This separation isn't only applied on screens; it's enforced in the database where the data lives.
Inside a company, not everyone sees everything either. Each branch, site, facility or line of work is opened as a separate project, and users only access records in projects they belong to.
Roles decide who can see and change what. Field staff see their own jobs; areas such as costs, reports and settings are visible only to people you authorize.
Who a job was assigned to, when it was closed and who edited it are recorded in the task's history. When you wonder why a job changed, you can look back.
Sign-in runs on a separate authentication server; passwords are not stored in the database that holds your business data.
Your developers can connect your own systems to CloudotNet by creating an API key. A key is shown in full only once when it's created and can be revoked at any time.
API keys guide →If your security team has further questions, write to us and let's go through our infrastructure and processes together.
Tell us about your work and we'll walk you through the right setup on screen. Or just give us a call.
Prefer to try it yourself? Create a free account →
Your details are used only to get back to you. KVKK Disclosure