Who uses Santix in a construction firm?
Santix has two layers of roles. At organisation level there are the owner, organisation admin and member; at project level each member joins a project as project manager, site manager, field engineer, architect / designer, subcontractor or viewer. The role decides which modules a person sees and what they can change. Permissions are enforced in the database: data hidden on screen is never sent from the server, so even a lost phone does not hold records its user could not see.
A typical mid-sized residential contractor sets up the team like this: the founder as owner, the office administrator as organisation admin, a project manager following two sites, a site manager and one or two field engineers on each site, an architect from the external design practice, a manager from each subcontractor, and a viewer from the building inspection firm.
Owner
Full rights on every project in the organisation. Buys and changes the subscription, approves payments above the threshold, sets budget visibility and can also approve revision requests. Typically checks project overviews, pending payments and expiring documents a few times a week. More on Santix for company owners.
Organisation admin
Invites people, assigns organisation and project roles, creates and manages projects and sets budget visibility. Sees the plan without prices and cannot change the subscription. Sees a project's drawings and tasks; to work with contracts, procurement, documents or budget on a project, they are added to it with a project role as well.
Project manager
Builds and imports the schedule, runs procurement and contracts, and reads and writes the budget at full level by default. Does not approve revision requests or payments. Usually the person following several sites: Santix for project managers.
Site manager
Owns the site: approves or rejects revision requests, approves subcontractor payments, runs the snag list and records progress. Sees the budget at full level by default. See Santix for site managers.
Field engineer
Reads drawings and drops pins, sees all pins, marks progress, starts revision requests, edits room data, raises purchase requests and adds documents. Does not see the budget or contract values by default; the owner can open the summary level if needed.
Architect / designer
Publishes drawing versions, answers revision requests and approves rooms and finishes. Sees all pins and reads the schedule and documents. Budget, contracts and bids stay closed: Santix for architects.
Subcontractor
Sees only tasks assigned to them and pins they opened, plus their own firm's contract and documents. Reads the drawings and reports finished work with a photo as awaiting inspection, but cannot close it: Santix for subcontractors.
Viewer
Reads drawings, rooms, pins, the schedule, revisions and documents but changes nothing. A fit for building inspection, the client or an investor's representative. Like every role, a viewer uses a seat.
Which role sees what? The full permission table
The table shows what each role can do in each module, taken from the app's permission list. Budget, contract values and bid prices are never inherited from a higher role; they appear only with an explicit permission.
- Full
- View, create, change
- Write
- View, create and edit
- Read
- View only
- Own
- Only records assigned to them, opened by them or linked to their firm
- –
- No access, section not shown
| Module | Owner | Project mgr | Site mgr | Field eng. | Architect | Subcontractor | Viewer |
|---|---|---|---|---|---|---|---|
| Plan, payment, subscription | Full | – | – | – | – | – | – |
| Creating invite codes | Full | Own project | Own project | – | – | – | – |
| Drawings | Full | Uploads | Uploads | Read | Uploads, publishes versions | Read | Read |
| Room data | Full | Write | Write | Write | Write, approves | Read | Read |
| Pins | Full | Edits any | Edits any | Sees all, opens | Sees all, opens | Own | Read |
| Closing pins | Yes | Yes | Yes | Own pins | Own pins | No | No |
| Raising revision requests | Yes | Yes | Yes | Yes | – | – | – |
| Approving revisions | Yes | – | Yes | – | – | – | – |
| Answering revisions | – | – | – | – | Yes | – | – |
| Marking progress | Yes | Read | Yes | Yes | Read | Read | Read |
| Schedule | Full | Write | Write | Write | Read | Own | Read |
| Contracts | Full | Write | Write | – | – | Own, read | – |
| Procurement and bids | Full | Write | Write | Raises requests | – | – | – |
| Budget (default) | Full | Full | Full | None | None | None | None |
| Payment approval | Above threshold | – | Yes | – | – | – | – |
| Official documents | Full | Write | Write | Write | Read | Own, read | Read |
The organisation admin has no column because their rights inside a project are limited: they invite people, manage the project and see drawings and tasks. To work with contracts, procurement or documents on a project, they are added to it with a project role. The payment approval threshold defaults to ₺500,000; above that lira value the owner approves after the site manager.
How is budget visibility set?
Budget visibility has three levels and is set by the owner or organisation admin per role or per person, for all projects or for one. The most specific rule wins: a person's level beats their role's. The owner always sees the full budget.
| Level | What is visible |
|---|---|
| None | The budget section does not appear |
| Summary | Planned, actual, pending and committed totals; no line or payment detail |
| Full | Budget lines, payments and payment breakdowns; can enter data |
Example: a senior field engineer gets summary level on "Ataşehir Blok B" only; on that project they see totals, on other projects the budget section does not appear. Changes are written to the audit log.
How is the team invited to a project?
Invites are made on the project's team screen. The owner, organisation admin, project manager and site manager can create invite codes.
- Tap invite and optionally fill in name and phone or email.
- Choose the role: project manager, site manager, field engineer, architect / designer, subcontractor or viewer. For a subcontractor, pick their firm; for an architect, a practice name can be added.
- Create the 8-character code. It is valid for 14 days and single-use, and leaves out I, O, 0 and 1 so it cannot be misread.
- Share it by WhatsApp, SMS or email. The person installs the app, creates an account and enters the code.
- They appear in the team list; pending invites are listed separately. Someone who leaves is removed from the project.
Every accepted invite uses a seat. When seats run out the code does not work and the person sees that the organisation's licence quota is full. More on team and invites.
Why are architects and subcontractors full users?
Architects and subcontractors are not guests in Santix; they sign in with their own accounts, so each one uses a seat. In return the architect answers revision requests in the app and uploads new versions directly, and the subcontractor sends finished work for inspection with a photo. Guest views opened from a link cannot record who saw and changed what; with full users every record belongs to a person.
Their roles are project-scoped, so organisation settings, billing and other projects stay hidden. Monthly prices per seat count are on the pricing page.
Which role should you give to whom?
| Person | Suggested role | Why |
|---|---|---|
| Partner, general manager | Owner (the organisation has one owner) or organisation admin | Only the owner manages the subscription; other partners become admins |
| Technical office, quantities and payments lead | Project manager | Writes budget and contracts, does not approve |
| Site manager | Site manager | Revision and payment approval |
| Field engineer, technical staff | Field engineer | Pins, progress, revision requests; budget closed |
| Architecture practice, interior designer, structural designer | Architect / designer | Publishes versions, answers revisions |
| Subcontractor manager, foreman | Subcontractor | Only their own work and contract |
| Building inspection, client representative | Viewer | Reads, changes nothing; budget closed |
Frequently asked questions
Can a subcontractor see other subcontractors' work?
No. A subcontractor sees only pins assigned to them or opened by them, and their own firm's contract and documents. They can read the drawings, but notes assigned to other firms are not shown.
Can one person have different roles on two projects?
Yes. Project roles are project-scoped, so the same person can be site manager on one project and project manager on another. The owner and organisation admin roles apply across the organisation.
Who approves a revision request?
The site manager or the owner. A field engineer, project manager or site manager raises it; once approved it goes to the architect, who answers with a note or a new drawing version, and the site manager closes it.
Can the project manager change budget visibility?
No. Only the owner and organisation admin change budget visibility. The project manager sees and writes the budget at full level by default.
Can an organisation have more than one owner?
The organisation owner is one person and manages the subscription. Other partners are added as organisation admins and given full budget access as individuals.
What is the viewer role for?
For people who should not change anything, such as building inspection, the client or an investor's representative. They read drawings, pins, the schedule and documents, and do not see the budget.
What if an invite code falls into the wrong hands?
Codes are single-use and expire after 14 days. Revoke an unused code from the pending invites list; if it has been used, remove the person from the project.