Core concepts

Assets, teams, private assets, owners and expiry status in Expira, and how they decide who sees an asset and who is alerted.

Assets

An asset is anything with an expiry date that you want to renew on time. Each asset has a type:

Type	Examples
SSL / TLS	Website and API certificates, ACM certificates
API Token	GitHub and GitLab tokens, deploy tokens
OAuth Secret	OAuth client secrets
IAM Key	AWS access keys
SSH Key	Deploy and server keys
Domain	Domain registrations, including Route 53
Code Signing	Apple certificates and provisioning profiles
Licence Key	Software licences and subscriptions

An asset also has an expiry date, an optional environment (production, staging or development), an owner, a renewal link and notes.

For an SSL certificate you can enter its hostname. Expira then reads the certificate from the host every day and updates the expiry date when it’s renewed. A host that can’t be reached keeps its last known date.

Team and private assets

• Team assets belong to a team. Every member of the team can see them, and team alerts go to the team’s channels and members.
• Private assets belong to you. They use your personal alert settings and channels, and only you get their alerts.

Organisation owners and admins can see every asset in the organisation, including other people’s private assets.

If a team asset has no team (for example because its team was deleted), only organisation owners and admins can see it, and they get its alerts by email.

Synced and manual assets

Assets found by an integration are synced. Their name, expiry date, link and notes come from the provider and can’t be edited in Expira; they update on the next sync. Assets you add yourself are manual and fully editable.

Expiry status

Status	Meaning
Expired	The expiry date has passed
Critical (red)	7 days or less left
Warning (amber)	30 days or less left
Healthy (green)	More than 30 days left

The dashboard groups assets by these statuses so you can renew by real risk.