Introduction to Octave AMS

Churches, alumni bodies, unions, clubs, cooperatives, nonprofits, staff associations — any group people belong to. Each association gets a workspace that holds its people and its work, with a public home on its own subdomain.

#What you can do

• Keep members and their membership state, organised into units such as chapters, branches, and ministries.
• Build forms from twelve field types and publish them; every published change becomes a new version.
• Review submissions through a clear path, with the right permission required at each step.
• Run events — public, members-only, or invite-only — with registrations, waitlists, and check-in.
• Grant access through roles made of explicit entity::action permissions.
• Reach members by email, SMS, in-app, and push, and keep an audit log of what changed.

#How it fits together

An association owns a workspace. Inside it, members belong to units, roles decide what each person may do, and every record — a member, an event, a submission — has a stable resource name that the relationship graph and search index point back to. The association's plan sets which modules are on and how far each can grow.

#Signing in

The application lives at app.octaveams.com. This website is the public home for Octave AMS; it doesn't store your association's data.

#Next steps