How to use Calenvy

Calenvy is built for teams that live in their calendar, email, and contacts. This post is a concise guide to getting value from it quickly—as an end user or as someone configuring it for your organization.

Create your account and sign in

1. Open your Calenvy site (your team’s hostname or calenvy.com for the hosted product).
2. Register with a working email—you’ll use it for invitations, reminders, and digests.
3. Sign in from the login page; if your org uses SSO or special auth, follow their link instead of a password.

Keep your profile email accurate: outbound messages and meeting notices depend on it.

Understand the basics: people, calendars, and messages

Most workflows revolve around three ideas:

You do not need to master every screen on day one. Start with calendar and inbox-style views your admin highlights.

Day-to-day usage

Calendar

• Add events with a clear title, time zone, and attendees when possible.
• Use descriptions for dial-in links, agendas, and prep—others see them on invites and reminders.
• If you subscribe to shared calendars, check which layer is yours vs team so you edit the right one.

Contacts

• Search before you add duplicates; merged records save everyone confusion later.
• Note phone, email, and tags your org cares about (region, role, account).
• When you link a contact to an account, reporting and scheduling stay consistent across the team.

Email helpers

Depending on setup, Calenvy may send confirmation, reminder, or digest mail. Respect unsubscribe links where shown; admins can adjust what goes to which cohorts.

Tips for administrators

If you deploy or configure Calenvy:

• Align domain, SMTP, and from addresses (live.py / environment) with DNS and SPF expectations so invites are trusted.
• Use staging or a restricted account before changing payment, email batch, or SSO-related settings.
• Document your org’s conventions (naming calendars, tagging contacts) in an internal wiki and link this blog article for onboarding.

Blog authors: Markdown is supported

Post title entries are still rendered as before (legacy Django template snippets if you use them). Body and tease fields are interpreted as Markdown and converted to HTML with safe mode enabled—raw pasted HTML is stripped so only Markdown-generated markup is emitted.

Examples you can paste into the admin:

Headings and emphasis

## Section

**Bold** and *italic* work. Use lists for steps.

Links and lists

- First step
- Second step

Read more on [our site](https://calenvy.com/).

Code (inline and fenced)

Use backticks for file.py and fenced blocks for longer snippets.

Getting help

• Prefer your internal support or success contact first.
• For product feedback, route through your account owner so it reaches the right team with context.

Welcome to Calenvy—stay organized, stay kind to inboxes, and keep your calendar the source of truth.