date-website

Members Admin Guide

Purpose

Manage member accounts, memberships, and subscription payments.

Member Accounts

Most people register themselves at /members/signup/. Those signups land in the admin as inactive users; review their details and activate them once payment/eligibility is confirmed. Only use the manual “Add member” flow below when you truly need to create an account on someone’s behalf.

1. Go to Members › Members (/admin/members/member/).
2. Add member:
   • Fill in username (ASCII letters, numbers, dots, underscores and hyphens only; older members whose usernames contain other characters can still be edited as long as the username is left unchanged), contact details, membership type, and optional groups.
   • Set a temporary password. Tick Send email if you plan to notify the member manually (system does not send the password automatically).
3. Edit member:
   • Update contact info, membership type, or group assignments as needed.
   • On SF, tick Gulispass utfört after the member completes the required duty/pass. Until then, ordinary, lifetime, and extra SF members are blocked from the picture and exam archives. The checkbox only appears on SF.
   • Use the actions menu to bulk Activate or Deactivate selected users.
   • is_staff is computed automatically from group membership (groups listed in settings.STAFF_GROUPS).
4. Password resets: direct members to the “Forgot password” link on the login page, which uses the custom reset form. A password reset does not remove the member’s two-factor devices or passkeys.
5. Delete member: deleting an account also permanently deletes the admin log entries where that member was the acting user, because the audit log points at the member record; entries recorded for other users stay untouched. Everything else that cascades from the member (subscription payments, votes, authored content) is deleted too, so you need the matching delete permission for those registered models, while a superuser is unrestricted. The history of a deleted member cannot be recovered, so deactivate instead of deleting whenever you only mean to revoke access.

Two-Factor Authentication & Passkeys

• Members can protect their account with an authenticator app (TOTP), passkeys, and backup tokens from their profile page. A passkey sign-in counts as two-factor verification, including for admin access.
• The member edit page shows read-only 2FA devices, Passkeys, and Backup token devices inlines (name, created, last used). You can delete individual authenticator apps and backup token devices there; passkeys can only be removed by the member or with Inaktivera 2FA.
• The 2FA column in the member list is ticked when the member has a confirmed authenticator app or passkey.
• Inaktivera 2FA (actions menu) removes all authenticator apps, passkeys, and backup tokens for the selected members. Use it when a member has lost their devices and is locked out; they can then sign in with their password and set up 2FA again.
  • It requires change permission on members.
  • Superusers among the selected members are skipped unless you are a superuser yourself.
  • Every use is logged with your user ID and the affected members.
• Verify the member’s identity before disabling 2FA: it is the recovery path for a lost second factor.

Membership Types

• Found under Members › Membership types. Each type has a description and a Behörighetsprofil (Freshman, Ordinary, Supporting, Senior, Member without voting rights). These profiles are referenced by other apps (e.g., Polls, Archive) to enforce permissions.
• SF signup asks applicants to choose Ordinarie medlem, Evig SF:are, or Extra medlem, and member administration offers the same three types. Ordinarie medlem and Evig SF:are use ordinary-member behavior outside the separate archive eligibility checkbox. Extra medlem behaves like an ordinary member everywhere except polls: they cannot vote in questions restricted to ordinary members or voting-entitled members (Endast ordinarie medlemmar / Endast röstberättigade medlemmar) because their profile has no voting rights. Publication collections restricted to selected membership types admit Extra medlem whenever the allowlist contains Ordinarie medlem (or Evig SF:are, which shares its profile), so no allowlist edits are needed. Provisioning does not delete historical membership types that may still be attached to existing records.
• Ordinarie medlem costs 15 euro and expires after one year. Evig SF:are costs 40 euro and does not expire. Extra medlem costs 15 euro and expires after one year.

SF Staff Access

• styrelse can administer all site app models except the complete members app.
• skattis, sekre, webbansvarig, and admin have full site app model permissions without becoming superusers.
• Inauta has full permissions outside the members app. In the member registry it can only show and edit Evig SF:are members. Inauta cannot access membership products or payments, create members, change membership types, or change member groups.
• Superusers remain unrestricted.

Subscription Products & Payments

1. Subscriptions define name, price, renewal cadence (days/months/years), and whether they expire.
2. Subscription payments record actual payments:
   • Use Add subscription payment to log membership dues.
   • Pick the member (searchable list), subscription type, payment date, and amount paid.
   • Date expires is calculated automatically from the subscription’s renewal settings.
   • List filters help you find expired vs active payments.

Functionary Roles & Assignments

Functionary roles and assignments are managed by the functionaries app. See the Functionaries Admin Guide.

Front-Facing Pages

• /members/login/: custom auth view using the Member model.
• /members/info/: members can edit their profile (first/last name, address, etc.).
• /members/signup/: collects new member requests (kept inactive until an admin activates them).
• /members/functionaries/: public functionary listing owned by the functionaries app.

Tips

• When demoting a member (e.g., from Ordinary to Senior), consider their access in other apps (archive, polls) that rely on permission_profile.
• Use export tools (e.g., admin changelist CSV) for periodic mailing list updates.

This site is open source. Improve this page.