How do you invite someone?
Nobody is added automatically from an email list or a contact book. Every join goes through an invite code created by someone allowed to invite: the owner, an organisation admin, a project manager or a site manager. The app interface is Turkish; labels are translated here.
- Open the project's team section ("Ekip") and tap invite ("Davet et").
- Pick the role: project manager, site manager, field engineer, architect / designer, subcontractor or viewer. The default is field engineer.
- Optionally add a name and phone or email, purely so you remember who the code was for.
- For a subcontractor, choose the firm from the procurement vendor list; for an architect, type the office name.
- Create the code. The screen shows the 8-character code with "valid 14 days, single use".
- Share it by WhatsApp, SMS or email. The message includes the organisation and project, the code and a link that opens the app.
The invitee installs the app, creates an account, enters the code on the join screen, and is added to the organisation and to the project in the chosen role at that moment.
How do invite codes work?
- Length
- 8 characters; 0, O, 1 and I are left out to avoid mix-ups
- Validity
- 14 days
- Use
- Single use
- Revoking
- Pending invites are listed on the team screen and can be cancelled
- Seats
- If the organisation's seats are full, the join does not happen
Codes are generated and checked in Santix's database, not in the app. Case and stray spaces are ignored. Someone previously removed or suspended who joins with a new code is reactivated rather than duplicated.
What happens when seats run out?
Every active user, architects and subcontractors included, takes a seat, and the limit is enforced in the database. If a code is entered while seats are full, the person sees: "Your organisation's licence quota is full. Please contact your organisation administrator." Settings › Members shows usage such as 5 / 5. To free a seat, suspend someone, remove them from the organisation, or have the owner move to a larger plan (5, 10, 25 or 50 users) under Settings › Plan and payment. Downgrading never suspends anyone; it only blocks new members. See pricing.
Organisation role versus project role
| Organisation role | Sees | Assigned by |
|---|---|---|
| Owner | All projects, budget, plan and payment; always sees the budget | Whoever created the organisation |
| Organisation admin | Manages all projects and members; sees the budget only if allowed | Owner |
| Member | Only the projects they were invited to | Owner |
Members join each project with one of six project roles and can hold different roles on different projects. On the team screen people are grouped by role, with company names under subcontractors. Anyone allowed to invite can change a project role or remove someone from the project; only the owner changes organisation roles.
| Project role | Can invite | Default budget | Typical work |
|---|---|---|---|
| Project manager | Yes | Full | Schedule, contracts, procurement |
| Site manager | Yes | Full | Revision and payment approval |
| Field engineer | No | None | Pins, progress, revision requests, documents |
| Architect / designer | No | None | Sheet versions, room approval, revision answers |
| Subcontractor | No | None | Own assigned items, own contract |
| Viewer | No | None | Reads sheets, items, schedule and documents |
The full matrix is on roles and permissions.
Who sees the budget?
Budgets, payment amounts and bid prices never pass down from a higher role. By default the owner, project manager and site manager see the full budget. Under Settings › Budget visibility the owner or an admin sets each project role to none (the budget section does not appear), summary (totals only) or full (lines, payments, approvals). The server enforces it, so budget rows never reach the device of someone set to none, and every change is written to the audit log. See progress payments and budget.
Who gets which notification?
| Event | Goes to |
|---|---|
| New item assigned to you | The assignee |
| Pin status changed, new comment | The pin's creator and assignee |
| Revision step: site manager approval, sent to architect, accepted or declined | The owner of the next step and the requester |
| Payment awaiting approval | The roles that must approve it, by amount the site manager and owner |
| Payment approved or rejected | Whoever entered it |
| Reminder: document expiry, contract dates | The reminder's target roles and people |
Notifications arrive as phone push messages and in the in-app list; tapping one opens the pin, revision or payment. Due reminders are checked every minute on the server. Choosing notification types per person is not available yet; you can switch Santix notifications off entirely in the phone's settings.
Example: staffing a site
A site manager starts on Ataşehir Blok B (ATB-02). The organisation has a 10-user plan with 4 seats in use. She creates field engineer codes for two engineers, an architect code for the design office, and subcontractor codes for the tiling and plumbing firms chosen in procurement. As codes are used, pending invites shrink and seat usage reaches 9 / 10. The owner then sets the field engineer role to summary in budget visibility, so the engineers see budget totals but not lines.
What does the audit log record?
Changes to the organisation, memberships, projects, project memberships, budget visibility, invites and the subscription are written automatically to an audit log with time, table and old and new values. Only the owner and organisation admins can read it. See security.
Limits
- No bulk invites or contact-list import; each code is for one person.
- No per-person choice of notification types yet.
- Sign in with Apple, Google and phone is in preparation; accounts currently use email and password.
- You create an organisation in the app with its name; a tax number is optional. New organisations start with 5 seats and a 3-day trial.
Frequently asked questions
How long is an invite code valid?
14 days, and it works once. Unused codes can be cancelled from the pending invites list.
Does a subcontractor take a seat?
Yes. Every active user, architects and subcontractors included, is a seat. Suspended people do not count.
What if a code is entered while seats are full?
The join does not happen and the person is told the licence quota is full. Free a seat or move to a larger plan.
Can one person have different roles on different projects?
Yes. Project roles are per project, and the person counts as one seat.
Can a field engineer see only budget totals?
Yes. Set the field engineer role to summary under budget visibility.
What should I do when someone leaves the company?
Remove them from the organisation under Settings › Members and invites. Their access to every project ends and the seat is freed; their records stay in the project.