Role-based access
Granular roles for admins, managers, and operators with least-privilege defaults.
Security & trust
Built to protect your operations and data.
Access controls, auditability, and transparent communication keep Plexidy dependable.
Controls
How we protect access and data
Auditability
Logged actions for schedule changes, billing updates, and authentication events.
Data handling
Encrypted in transit and at rest; scoped data exports with expiration.
Incident response
Clear runbooks, status communication, and customer notification pathways.
Operational commitments
Uptime target
99.95% platform availability.
Transparent updates
Changelog, release notes, and status posts for every meaningful change.
Access reviews
Regular reviews of admin access, tokens, and integration keys.
Contact channels
Reach the right team for security or account concerns.
Audit events we track
Event
Recorded details
Login
User ID, timestamp, IP, method (password/OAuth).
Role change
Actor, target user, old/new roles.
Schedule change
Appointment ID, previous state, new state, actor.
Billing update
Changed fields, actor, related invoices.
Operational depth
Evaluate trust controls with operational consequences in mind
Security content here should frame access boundaries, governance responsibilities, and incident communication expectations in operational terms.
Primary audience
Security reviewers, compliance stakeholders, and workspace administrators
Decision focus
Validate whether controls, policies, and response posture meet internal governance requirements
Operational risk
Assuming baseline security language equals practical control maturity can expose rollout risk
Field scenario
A compliance lead reviews whether role boundaries and escalation paths are sufficient for regulated workflows.
Execution walkthrough
1. Frame the objective
Security content here should frame access boundaries, governance responsibilities, and incident communication expectations in operational terms.
2. Align participants
Security reviewers, compliance stakeholders, and workspace administrators
3. Validate the decision
Validate whether controls, policies, and response posture meet internal governance requirements
4. Mitigate known risk
Assuming baseline security language equals practical control maturity can expose rollout risk
Interpretation matrix
Signal
Interpretation
Operational scenario
A compliance lead reviews whether role boundaries and escalation paths are sufficient for regulated workflows.
Successful outcome
Successful use of this page leaves teams with clear direction on Validate whether controls, policies, and response posture meet internal governance requirements.
If skipped
Skipping this step often introduces Assuming baseline security language equals practical control maturity can expose rollout risk.
Recommended next step
Cross-check this with privacy and terms pages to confirm legal-policy consistency.