Member properties let you remember useful information about the people in your community: interests, cohort, location, goals, payment status, experience level, or anything else you need to organize with care. Once a property exists, Sutra can use it across contacts, members, invitations, broadcasts, exports, and other targeted workflows.
Before you start
You need management access to create, edit, reorder, or delete property definitions.
Properties belong to the community context, so they can be available across nested spaces in that community.
Contact and member data can include personal information. Use properties thoughtfully and only collect what you need.
Create a member property
Open the members or people settings for your community.
Open the member property settings.
Add a new property.
Give it a clear name.
Choose the property type.
Add options if you are using a select or multi-select property.
Save the property.
Supported property formats include text, select, multi-select, number, date, URL, location, phone, person, space, image, video, and file.
Add values to people
You can add property values in several ways:
Edit a member or contact profile as a manager.
Map columns during a CSV contact import.
Collect answers through registration or survey workflows where member-property questions are used.
Set or update property values through automations where that action is available.
Use the API where your token and permissions allow it.
When a contact later becomes a member, Sutra keeps their existing property values and links them to the user. You do not need to recreate that information from scratch.
Use properties as filters
Properties become useful when they help you find the right people. You can filter members or contacts by property values, then use those filters in places like invitations, broadcasts, exports, or other people workflows.
Saved filters describe rules, not a frozen list of people. If members join, leave, or update their property values, the people matching that filter can change.
How properties work in nested spaces
Properties are shared from the top-level community into nested spaces. That means a property you create for the community may appear while you are managing a child space.
Values still belong to the resolved community context, which helps Sutra avoid splitting one person's information across a dozen disconnected places.
What happens next
After your properties are in place, you can use them to make your communication and member care more specific. For example, you might invite only people in a certain cohort, send a broadcast to people who selected a particular interest, or export a filtered list for review.
Troubleshooting
If a property appears in a child space, it may be inherited from the top-level community.
If an option count looks lower than expected, some members may not have a value for that property or may not be active in the current scope.
If a saved filter changes, check whether the underlying members, contacts, or property values changed.
If an imported value did not appear, check the CSV mapping, email validity, and whether the property exists in the target community.
If an integration is filtering by property, use the stable property ID or configured key rather than relying on the display name.