Limitations
- Non-text custom fields are view-only. Members can see non-text custom fields you expose, but they cannot edit them — only text custom fields are member-editable.
- Membership Portal permission is required. The Login Portal settings are hidden unless your user group has the Membership Portal permission enabled in Settings → Users & access → User groups.
- Page security depends on Umbraco. Login groups only control website access once they are synced to Umbraco and page permissions are assigned there. Building a group in SwiftFox alone does not secure any pages.
- Group changes require a sync. After editing or deleting login groups, you should re-run Sync membership groups so Umbraco reflects the latest definitions.
- Financial tables show only selected columns. Members only see the financial columns you enable under Financial tables on the Subscription Management tab; anything not selected is hidden.
Best practice
- Plan your login groups before syncing. Decide on your membership segments and build the corresponding login groups first, then sync once to Umbraco and assign page permissions — this keeps the website access model clean.
- Expose the minimum fields needed. Only make profile, address and custom fields visible and editable where members genuinely need self-service, to reduce the risk of unwanted edits.
- Use a familiar Secondary ID. Choose a Secondary ID (such as member number) that members are likely to know, to smooth the passwordless login experience.
- Review financial columns for clarity. Show the financial columns that help members understand their status (for example Arrears, Auto renew, Status) without overwhelming them with detail.
- Keep event RSVP options consistent. Enable portal RSVP options that match how your team manages events internally so reporting stays clean.
- Re-sync after changes. Treat Sync membership groups as a required step whenever group definitions change.
Related guides
- Subscription & payment management in the Login Portal (Document ID: 352)
- Profile fields shown in the portal (Document ID: 353)
- Portal events (Document ID: 345)