Every person on the team sees exactly what they need for their work.

Every employee sees the workspaces that match their responsibilities. Changes remain attributable to one person, sensitive data is limited and operations no longer depend on a shared password passed around the team.

With a shared login, it is impossible to know who changed a booking or to handle one employee leaving securely. Personal accounts provide accountability, targeted permissions and clean deactivation without changing the password for the whole property.

A role groups the permissions required for a real hotel job. The property assigns employees to the appropriate role, making it possible to separate front desk, housekeeping, finance and administration clearly.

STRYK provides practical starting roles for typical responsibilities, including owner, administration, front desk and housekeeping. The property reviews them against its operation and creates additional roles where responsibilities differ.

Only expressly authorised administrators manage accounts and permissions. This function does not belong in a general employee role because it determines who may view or change guest, booking, finance and configuration data.

Each role sees only what it needs for the job. Housekeeping stays focused on rooms and tasks, while finance manages documents without automatically controlling users or property settings.

The property creates a personal user with a unique email address, assigns the appropriate role and verifies the first sign-in. Only then is the account used in the real workspace; shared temporary accounts are unnecessary.

The personal account is deactivated specifically. Historical actions and operational assignments remain traceable while the person can no longer access the hotel; other employee accounts and passwords remain unaffected.

Yes. Sign-in runs via Nextpulse ID, where each person sets up their second factor. For sensitive actions, STRYK additionally requires a fresh sign-in with the second factor.

Staff maintain their profile, photo and language in STRYK themselves. They manage their password and second factor in their Nextpulse ID account. Hotel-wide roles and permissions remain the responsibility of hotel management.

Personal user identities and the STRYK activity log connect relevant actions with time, area and responsible account. This supports handovers, questions and corrections without relying on memory or chat histories.

No. Access to operational history follows the role. Employees see the information required for their work, while comprehensive review and administration views remain reserved for appropriately authorised roles.

Yes, in the STRYK app for iPhone and Android and in the browser. There, too, the role and permissions of the personal account always apply.

A personal language preference can differ from the property default. A multilingual team can therefore work in the same hotel environment without mixing employee language with guest, document or public website language.

Yes. Especially when a few people cover many jobs, a simple role structure creates clarity. Owner, front desk and housekeeping are often enough to begin with; personal accounts and deliberate sensitive permissions matter most.

A test user completes the role’s most important jobs and also attempts an intentionally prohibited action. The test succeeds only when required work is possible and unrelated sensitive areas are genuinely blocked.

Yes. When responsibilities, seasonal staffing or operating structure change, the property can adjust roles and user assignments under control. Sensitive permission increases should always have a clear operational reason and a short functional test.

The daily plan connects every room with its status, tasks and responsible person. Employees see their assignments, start work and report finished or ready directly on the room without another paper list.

Booking state, room releases, housekeeping assignments, open balances and relevant activity remain visible on the appropriate record. The next shift continues from the current state instead of rebuilding it from private chats or individual notes.

Rollout begins with a role matrix, personal accounts and one real hotel workflow per role. Documentation and support check not only sign-in but whether employees can complete their work while unrelated sensitive areas remain blocked.

Users, roles and their STRYK workspaces are part of the single STRYK offer. There is no setup fee or hidden STRYK module tier; external device, mobile network or partner costs may still apply independently.

For each real job, the property records who may manage bookings, guests, rooms, housekeeping, pricing, finance, reports, settings and users. It also documents deputies and which permissions are explicitly not granted.

In your demo access you compare two employee roles: which tasks they may complete, which sensitive areas remain protected and how an account is deactivated.