One employee record underneath
Every module reads the same person, the same team and the same permissions. Switching one on adds capability rather than another system to keep in sync.
Resources
How Crewzy fits together, and how it is protected.
Understand how the modules work together, how application controls support your workspace, and where to find our privacy and service information.
How modules work
Add a module, not another integration.
Every module runs on the same employee record and the same permissions, so switching one on adds capability instead of another system to wire up and keep in sync.
Permissions travel with the person
Access is evaluated from company-scoped role grants, so turning on a module never means re-granting everyone access to it separately.
Turn one on, turn one off
Modules are enabled per company. What you do not use stays out of the way instead of cluttering every screen.
Data crosses without an integration
Approved leave reaches the timesheet, approved time reaches the invoice. No connector to configure, no sync to monitor, no mapping to maintain.
Security & trust
Security at Crewzy.
Crewzy’s primary database and document storage are hosted on AWS in London, UK. We use HTTPS, encryption at rest, a private database network and protections against public access to stored documents. Automated database backups, threat detection and infrastructure audit logging are enabled. Further security and data-processing information is available on request.
Access permissions, approval controls and activity history are part of Crewzy’s application design.
Company-scoped access
Roles, company permissions and record ownership checks govern access to records and actions.
Approval controls
Supported workflows separate the person raising a request from the person approving it.
Activity history
Recorded actions include the actor, outcome and time, helping teams review changes.
Account protection
Password hashing, optional multi-factor authentication and failed sign-in controls support account security.
Controlled document access
Authenticated requests, company permissions and time-limited download links govern access to uploaded documents.
Service protections
Application controls include security headers, request rate limits and production-secret checks.
Using AI thoughtfully
Relevant context. Human judgement.
AI can help with workspace questions, document fields and summaries where enabled. Use relevant information and review the results.
Permission-aware context
Where AI features are enabled, workspace tools use company and role permissions to retrieve relevant information. Inputs and relevant context are processed by the configured AI provider.
Careful inputs and review
Share only the information needed for the task. Keep passwords, sign-in codes and tokens out of prompts and uploads. Check generated answers, summaries and extracted fields before acting on them.
Privacy & service information
Understand how your data is used.
Read how Crewzy handles account and workspace information, the terms for using the service, and the arrangements for customer-controlled data.
Information in one place. Our privacy and service pages explain the relevant scope, responsibilities and current provider information.
Compliance support with a clear scope. Crewzy tracks document dates and expiry and helps organise compliance evidence. It does not verify document authenticity or guarantee regulatory compliance.
Discuss your security requirementsReady when you are
Explore Crewzy with your team.
Explore the connected workflows, or request a demo to discuss your team’s requirements.