Everyone with their own login. Every hotel with its own data.
Your team signs in with Nextpulse ID and only sees what their role allows. We keep each hotel’s data separate in the database, encrypt sensitive details and record important changes in the activity log with person and time. That way you give the new receptionist access without passing on a shared password.

Nextpulse ID
One personal login for everyone. STRYK keeps no staff passwords.
Roles and permissions
Granular permissions per role, plus access per module.
Separate hotels
Row-level security in the database keeps each hotel’s data apart.
Traceable
Sign-ins, permission changes and data changes appear in the activity log.
One Nextpulse ID login instead of a password on a sticky note.
Staff sign in exclusively through Nextpulse ID; we deliberately keep no staff passwords in STRYK. During a shift the session renews quietly in the background. Anyone can add a second factor at Nextpulse ID, and your hotel can require it for all roles.
- Nextpulse ID with OIDC and PKCE
- Silent session renewal
- Two-factor for all roles as a hotel decision
- Screen lock with workstation PIN
Reception takes bookings, accounts closes the books. Each with their own rights.
Roles bundle granular permissions per area, from bookings and housekeeping to finance, channels and settings. Whoever grants permissions can only grant what they have themselves. STRYK checks role permissions and module access on the server with every request, not just in the interface.
- Standard roles and custom roles
- Permission ceiling when granting
- Owner rights for contract, ownership and payout account
- Module access on top of the role


A hotel’s data stays with that hotel.
Every request runs in the context of exactly one hotel, and the database also enforces this separation with row-level security. We encrypt sensitive fields such as credentials for registration authorities or key box codes for their specific purpose. STRYK scans uploaded files such as supplier invoices or chat attachments for viruses.
- PostgreSQL row-level security per hotel
- Purpose-bound encryption of sensitive fields
- Virus scanning for uploads
- API keys only valid for one hotel
Who changed what, and when. The answer is in the log.
The activity log records changes with person, time, area and the record affected, including role assignments. When we, the STRYK team, help in your hotel, we appear with our own support code and time-limited access. When someone leaves, you remove their access, their sessions end and the history remains.
- Filter by period, area, action and person
- Export as PDF, CSV or XLSX
- Support access visible and time-limited
- Removing access ends every session
From the first working day to leaving.
A personal login stays with each person throughout their time at the hotel.
- 01
Add the person
Enter name, email and role. Sign-in runs through Nextpulse ID.
- 02
Check permissions
The role shows which areas the person can view, edit or manage.
- 03
Work
Every important change carries the person’s name in the activity log.
- 04
Remove access
When someone leaves, access ends and earlier changes stay assigned to them.
Who is responsible for what.
Owner
Keeps contract, ownership and payout account in their own hands. Owner logins are protected from removal.
Admin
Has every permission except owner rights, assigns roles and manages devices and API keys.
Team
Signs in with their own Nextpulse ID account and sees exactly the areas of their role.
Security in every area.
The same data separation applies in the browser, in STRYK Desktop, in the STRYK app and in the Partner API. We built in no exception.
Common questions: Data protection & access
How does STRYK protect hotel operations?
Every employee works with a personal account and exactly the permissions that match their job. Two-factor sign-in, separated property data and traceable history protect guests, finance and teamwork every day.
Does each property’s data remain separated?
Yes. Bookings, guests, rooms, finance and settings remain assigned to the signed-in property. Data from other properties appears in neither lists nor detail views.
Why does every employee need a personal account?
Only a personal account links a change clearly to the responsible person. Shared reception passwords make access removal, handovers and traceability harder and should therefore not become the operating model.
Which standard roles are available?
STRYK provides clear starting roles for owner, administration, team and housekeeping. They reflect typical responsibilities in small and medium properties; actual access remains reviewable in the visible permission matrix.
Can the property create custom roles?
Yes. A custom role receives a name, description and exactly the required module permissions. A night manager can therefore edit bookings and read reports without automatically managing payment methods or users.
How detailed are permissions?
The matrix separates bookings, rooms, availability, housekeeping, guests, messages, finance, pricing, Booking Engine, channels, reports, settings, users, roles, POS and registration, among others. Each area distinguishes reading, editing and management where the workflow requires it.
Show more questions
Does STRYK prevent contradictory permissions?
Dependent permissions are handled together: anyone who manages an area needs the required reading and editing foundation. When permission is removed, STRYK removes dependent grants under control rather than leaving an unusable partial role.
Which details does a new user require?
Name, a unique email address and an active role. The hotel does not issue a starting password: the person receives an email and sets their own login details with Nextpulse ID. An email address can belong to only one STRYK user account.
Which password rule applies?
Passwords are not set and checked in STRYK, but with Nextpulse ID; the password rules apply there. STRYK does not issue or store passwords for staff.
How is a departing employee’s access ended?
Management disables that individual account. The former employee can no longer sign in, while previous tasks and changes remain assigned to the right person.
Can a user accidentally deactivate themselves?
No. STRYK blocks self-deactivation in team management. An administrator therefore cannot end their own ability to work in the middle of role maintenance.
Can the last owner be removed or downgraded?
No. Before an owner is deactivated or assigned another role, STRYK requires another active owner. This protects the property from locking itself out of full administration.
Can the owner role be deactivated?
The central owner role remains active and retains full responsibility. A user also cannot remove from themselves the role permissions needed for continued user and role administration.
Can a role be changed later?
Yes. An authorised administrator assigns the employee another active role. The change is attributed to the user and responsible operator and applies to subsequent protected actions.
What happens to a role that still has active users?
STRYK prevents uncontrolled deactivation. Affected employees must first be assigned a suitable active role or deliberately deactivated.
How is two-factor sign-in set up?
Each person sets up their second factor in their Nextpulse ID account, for example with an authenticator app. STRYK accepts the verified sign-in from there.
What happens at login when two-factor sign-in is enabled?
Sign-in runs via Nextpulse ID: email, password and second factor are confirmed there, and only then does STRYK open access to the hotel. Your hotel decides whether a second factor is required for all roles. Once signed in, each person works with the permissions of their role, without signing in again for individual actions.
How is two-factor sign-in disabled again?
This is done in the Nextpulse ID account, not in STRYK. If someone has lost their second factor, STRYK support can reset it after verification.
What happens when a sign-in expires?
STRYK visibly ends access and asks for a new sign-in. A disabled employee cannot regain access, while active users sign in securely again.
How does “forgot password” work?
Passwords are reset with Nextpulse ID, not in STRYK. STRYK itself does not manage passwords for staff.
Which security changes remain in the activity log?
Sign-ins and the creation and modification of users and roles are logged with hotel, user and action. This makes it possible to clarify later who changed an access right. Password and second factor are managed with Nextpulse ID.
How does STRYK support guest-data privacy?
Guest photos can be centrally disabled or deliberately removed. When a guest record is deleted, STRYK anonymises personal data if existing booking references must remain; without such references the record can be removed completely. The action is logged.
Do roles, two-factor sign-in or privacy cost extra?
No. Users and roles, sign-in with a second factor and the data protection features are part of the STRYK price, with no set-up fee and no surcharge. In your demo access you review the role matrix and personal accounts yourself.
See who can do what in your hotel.
Try STRYK for 14 days with your team, or we will show you roles, permissions and the log in a demo.