Protection for guest and hotel data.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Management disables that individual account. The former employee can no longer sign in, while previous tasks and changes remain assigned to the right person.

No. STRYK blocks self-deactivation in team management. An administrator therefore cannot end their own ability to work in the middle of role maintenance.

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.

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.

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.

STRYK prevents uncontrolled deactivation. Affected employees must first be assigned a suitable active role or deliberately deactivated.

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.

Sign-in runs via Nextpulse ID: email, password and second factor are confirmed there, and only then does STRYK open access to the hotel. For sensitive actions, STRYK requires a fresh sign-in with the second factor.

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.

STRYK visibly ends access and asks for a new sign-in. A disabled employee cannot regain access, while active users sign in securely again.

Passwords are reset with Nextpulse ID, not in STRYK. STRYK itself does not manage passwords for staff.

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.

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.

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.