Skip to main content

User status explained

Updated over a week ago

The coapp user status is a powerful tool to manage a member's access to your community. coapp also has some automations that will help you reduce manual work.

What user statuses exist and what do they mean?

Active

The user is active and has full access to the community. This is the default state for all completely registered users.

Automation with coapp payment feature enabled

When the user creates a valid subscription their status will automatically be changed to "active".

Pending

The user's registration is not completed and the user can log in but has only access to their own account and payment settings. This status usually indicates that an admin needs to accept the user's registration to complete it.

Automation with coapp member confirmation feature enabled

All new users will automatically have this status until they have been accepted or rejected by an admin.

Suspended

The user's account has been temporarily suspended. The user can log in but has only access to their own account and payment settings. This status indicates that there is a problem with the account that must be resolved before the user can use the community.

Automation with coapp payment feature enabled

When the subscription status in Stripe changes to "unpaid" due to a failed payment, the coapp user status is automatically changed to "suspended". You can configure when a subscription becomes "unpaid" directly in your Stripe settings by defining the rules for overdue subscriptions and dunning behavior. Go to Stripe settings.

Cancelled

The user's account has been cancelled. They can still log in to access their account and billing history, but are not able to access the community.

Automation with coapp payment feature enabled

When the user or admin cancels a subscription, the user status will change to "cancelled" once the cancellation takes effect.

Guest NEW

Guests are people who have purchased tickets to an event but are not fully registered members of the community. They can access only the specific event content tied to their ticket.

  • Minimal registration (e.g. name, email at ticket purchase)

  • Access limited to the specific event

  • No access to messaging or member directories

  • Guests are included in the community member limits

This role helps open events to the public without giving full access to the internal community.

Did this answer your question?