Security Calendar
What expires, renews, rotates or lapses, and when, across your credentials, access, devices, DevOps policies and billing, plus your own events and task deadlines, with reminders before anything is due.
Solo Pro Team Business Enterprise
The Security Calendar answers one question: what will hurt if I miss it, and when? It brings
every security date PulsVault knows about onto one timeline: credential and API-key expiry, access
and share lapses, DevOps policy end dates, device trust, your organization's password and two-factor
deadlines, renewals, rotation policies and scheduled deletions. Your own events and your
task deadlines sit beside them. Open it from Security
Calendar in the sidebar, or at /console/calendar.
At a glance#
The strip at the top counts deadlines: things that lapse unless someone acts.
| Segment | Counts |
|---|---|
| Overdue · last 90 days | Deadlines that have already passed |
| Next 7 days | Deadlines due within a week |
| Next 30 days / Next 90 days | Deadlines due within a month, or a quarter |
Each segment shows how many of its deadlines are critical (due within 24 hours, or past) and how many are a warning (due within 7 days). Select a segment to list exactly those; select it again to go back.
A validation path that is failing right now is an ongoing issue, not something overdue, so it is listed under Ongoing issues and never counted in the strip. Scheduled validation runs are not counted at all: they run by themselves.
Views#
| View | Shows | Key |
|---|---|---|
| Horizon | The default. A list of what needs doing, soonest first: Ongoing issues, Overdue, Today, Next 7 days, Next 30 days, Later. Each row says what it is, where it lives and when. | 1 |
| Month | A month grid. A day's scheduled validation runs appear as a small count in the corner of the day. | 2 |
| Week | One week, with room for everything on each day. | 3 |
| Year | The next twelve months, each day shaded by how many deadlines fall on it, so a renewal season or a batch of keys expiring together stands out. Select a day to open it. | 4 |
On a phone the Horizon is the easiest view to read; every row's actions stay visible.
Filters#
Filters live in the address bar, so a filtered view can be bookmarked or shared and Back undoes the last change.
- Sources: Credentials & keys, Access & sharing, Identity, Billing, Validation, Data lifecycle, My events, Tasks.
- Severity: All, Critical, or Warning and above.
- Project or vault: narrow to one project (with the vaults it holds) or one vault. Account-level dates (billing, devices, your own roles) stay visible whatever you filter to, because they belong to no project.
- Search: by title.
What appears#
| Source | Dates |
|---|---|
| Credentials & keys | API keys expiring under your machine identities · expiry dates recorded on cards, passports, licences, memberships and tokens · rotation cadences you set on an item's Lifecycle tab |
| Access & sharing | Role and permission grants that expire · shared access and secure links that expire · invitations you sent that will lapse · DevOps access policies, and a machine's hold on one, that stop granting access |
| Identity | When a trusted device stops unlocking your vault · when your organization requires a new master password · when your organization requires two-factor authentication from you |
| Billing | Renewal, or the end of a plan that will not renew · trial end · when a lapsed plan's read-only window closes |
| Validation | Paths that have stopped validating · configs switched off because their path is empty · when a snoozed alert wakes again |
| Data lifecycle | The day a scheduled account deletion erases everything · the last day a deleted project can be restored |
Each date is shown on the day it falls in your time zone. A date with no time (an item's printed expiry date) is the same date for everyone.
Your calendar shows your subscription, the shares and links you created, API keys and policies you manage, expiry dates on your items and the deadlines your organization's policy sets for you. Items in vaults shared with you appear on their owner's calendar. Validation follows your whole space: in an organization you see every project's failing paths, the same view as the project's own Validation screen.
Acting on a date#
Select any row or marker to open its panel. It names exactly what the date is, when it falls (and why it is critical or a warning), what you are expected to do, and offers:
- Open source: jumps to where the date is managed: the item, the machine identity, the policy library, your devices, billing or the project's settings.
- Create task: for dates you can act on, opens a task with the title and due date filled in. A critical one starts at High priority.
- Mark rotated: on a rotation that is due, when the item is yours and its vault is unlocked. It restarts the cycle from today.
Security dates are read-only on the calendar: each mirrors a date stored elsewhere, so you change it there and the calendar follows.
Your events#
- Choose New event (or press
N), or select a day in Month or Week. - Start from a template (Rotate credential, Access review, Recovery drill, Backup restore test) or type a title.
- Choose All day or a time. Times are in the time zone shown under the fields, which is your Preferences time zone or your browser's.
- Optionally Repeat it weekly, monthly, quarterly or yearly, until a date of your choice; link it to a project or vault; and set a reminder.
- Choose Create event. Select it later to edit or delete it.
A repeating event is one series: editing any occurrence changes them all, and a monthly event set on the 31st falls on the last day of shorter months. Drag a one-off event to another day in Month or Week to move it.
Unlike vault items, an event's title and notes are stored readable by PulsVault so reminders can be sent. Never put a password, key or other secret in them.
Reminders#
A reminder posts to your notification center ahead of time: 15 minutes, 1 hour, 1 day, 3 days or a week before (the shorter ones are for events with a time). A repeating event reminds you before every occurrence; if PulsVault was unreachable when one was due, you get the next one, not a backlog.
Security dates have their own reminders: API keys are announced 30, 14 and 3 days ahead and on the day; DevOps access policies 14 and 3 days ahead and on the day; a deleted project 3 days before it is purged and on the day.
Export to another calendar#
⋯ → Export to calendar (.ics) downloads what you are looking at, with the current filters. By default the file holds only kinds and dates, such as API key expiry, so it is safe to import into any calendar app. Export with details adds titles, project and vault names, notes and links: choose it only if you are comfortable with those leaving PulsVault in the file.
Organization view#
Members who can see the organization's Security Center get a Mine | Organization switch. The organization view shows the dates the organization must not miss:
- members' expiring roles and permissions
- every machine identity's API keys and DevOps policies
- pending invitations
- who must enrol in two-factor or change their master password, and by when
- a failed backup-archive run
Facts about many members on the same day are grouped: 12 members must enrol two-factor opens to the list of names. Billing dates appear only for members who can see billing, and backup details only for those who manage backups. Personal events and personal items never appear here.
Keyboard shortcuts#
| Key | Action |
|---|---|
N |
New event |
1 – 4 |
Horizon, Month, Week, Year |
← → |
Previous or next month or week |
T |
Today |
/ |
Search |
? |
Show the shortcuts |
Availability#
The calendar follows the Task Workflows entitlement: Solo Professional, Team, Business and Enterprise. See Plan comparison.
Related#
- Task Workflows: where due dates, priorities and status live
- Projects: projects, vaults and machine identities
- Plan comparison: which plans include the calendar
Common questions#
| Question | Answer |
|---|---|
| Why can't I move a security date? | It mirrors a date stored elsewhere. Use Open source and change it there; the calendar follows. |
| I rotated a credential. Why is it still due? | Use Mark rotated (here, or on the item's Lifecycle tab). It restarts the cycle and re-arms the reminder. |
| Why does "Overdue" say "last 90 days"? | The calendar reads a window of dates, so it can only vouch for what is in it. Anything older is still on the screen it came from. |
| A path has been failing for a week. Why isn't it overdue? | It is an ongoing issue, not a deadline, so it is listed under Ongoing issues until it is fixed. |
| Why do I see "Partial view"? | One kind of date could not be loaded this time, and the banner names it. Everything else on screen is complete; Retry asks again. |
| I'm in an organization. Whose validation do I see? | Your organization's, the same as each project's Validation screen. |