Skip to content

System records, notifications, audit, and reference data

New staging website. Use https://beti.worldyogaalliance.org/admin/system and the linked staging reference routes after administrator sign-in.

Choose System in the Admin workspace sidebar or open /admin/system. The tabs are Notifications, Audit log, OTP records, and Legacy records. Admin accounts is a superuser-only system view; the Groups role manager is linked separately under Authentication and Authorization.

The sidebar’s Cities_Light, Schools, Teachers, Events, Invoices, Orders, Payments, and other groups link to reference workspaces. A row marked read-only is an inspection screen; do not attempt to change it through an unsupported URL.

The Notifications screen creates a notification for one existing member; it is not a broadcast tool.

  1. Select Create notification.
  2. Enter the numeric Member user ID.
  3. Enter Message (required, up to 5,000 characters).
  4. Enter Notification type (up to 100 characters).
  5. Enter an optional positive Reference ID.
  6. Set the required Notify at date and time.
  7. Optionally enter Custom URL or relative path. Relative paths must be safe /... paths, or use an http(s) URL approved for the member.
  8. Check Read only when the notification should start as read.
  9. Select Create notification.

For an existing row, select Edit notification, change the fields, and select Save changes. Use Delete only after checking the recipient and message. Verify the member ID before saving; a notification to the wrong user cannot be recalled from this screen.

After creating or editing a notification, reopen the row and verify the intended recipient, message, schedule, and read state.

The current staging workspace exposes access management through Authentication and Authorization → Groups, Users, and Admin accounts, plus read-only OTP records, Audit log, and legacy OAuth/social records. It has no separate general Security settings page in the source inventory. Use the access workflows in Sign in, roles, and administrator access and do not claim that an unsupported security toggle or session policy is available.

Audit log is read-only. It shows When, Actor, Action, Object, and Details. Actions include Added, Changed, and Deleted.

Use the log to correlate a recent write with the administrator and record. It is not a complete history for older legacy records and should not be used to infer a payment settlement, email delivery, or deployment event.

Use the audit table to correlate a recent write with the administrator and record.

Supervised support can use OTP records to inspect OTP verification records, with Identifier, Channel, Status, Attempts, Created, and Expires. Verification codes are hidden. This screen is read-only and superuser-only; never ask a member to paste a code into a ticket.

Use this read-only view for status and expiry checks; verification codes remain hidden.

Legacy records is a read-only inventory for older authentication and integration records. The resource selector can include:

  • Email addresses and Tokens.
  • Logging.
  • Django OAuth Toolkit Access tokens, Applications, Grants, and Refresh tokens.
  • Python Social Auth Associations, Nonces, and User social auths.
  • Social Accounts Social accounts, Social application tokens, and Social applications.

OAuth Access tokens and Refresh tokens expose a revoke action where the screen supports it. Revoke only an identified, compromised or expired token after confirming the owning account and impact. The screen does not expose token values in these guides.

These records belong to the legacy integration inventory. They are not the new administrator session, not member password storage, and not evidence that the legacy Django admin has been migrated. See Legacy Django admin inventory.

If the screen exposes a revoke action, confirm the owning account and impact before selecting it. Reopen the row to verify the result.

Open System → References or a reference link in the sidebar. The reference manager supports search, pagination (50 rows per page), and an editor with Add record, Save changes, and Delete where the configuration is writable. Read-only resources show no add control.

Use the exact resource label shown in the sidebar. Current reference groups include:

  • Schools: School types, School level, Level additionals, Training types, Style of yoga, School list teacher, Main teacher certifications, Main teacher teaching, Issue certificate, School statuses, and registration level/style resources.
  • Teachers: Teacher types, Type Applies, Style of yoga, Teacher level, Experience Years, Teacher Backgrounds, Teacher statuses, and registration resources.
  • Events: Event statuses, Booking Statuses, Event Option Categories, Event Options, Event Facilities, Studio Facilities, Custom Event Options, Event Images, Event Instructors, and event selections.
  • Commerce: Order Statuses, Invoice Statuses, Payment Providers, Payment method, Payment status, and Payment type. Provider records are read-only in the shell.
  • Locations: Cities, Countries, Regions/states, and SubRegions.
  • Other records: Sites, Profiles, Galleries, Testimonials, Graduates, and Platform Event Attendees.

Depending on the resource, the form can expose Name, Code, Prefix, Slug, Description, Icon, Category, Color, Active, Required, Multiple choice, Requires details, Default, Confirmed, Cancelled, Completed, Ordering, Price USD, Price EUR, Price THB, Price INR, Hours, Level type, Category ID, Event ID, English name, Thai name, Simplified Chinese name, Title, Image path / URL, Custom name, Custom image path / URL, Bio, Notes, Parent ID, Related ID, User ID, Primary, Highlighted, Confirmed at, Domain, Website URL, Phone number, Detail, Avatar, Receive emails, ASCII name, Display name, Code 2, Code 3, Continent, TLD, Timezone, Latitude, Longitude, Population, Country ID, Region ID, Subregion ID, First name, Last name, Email, Graduate number, Graduation date, social URLs, and Teacher level IDs (comma separated).

Only enter fields that belong to the selected resource. For IDs, choose the linked record from the current reference data or verify it before saving. Use Active/visibility flags to retire a value while preserving existing history where possible.

Gallery, testimonial, graduate, event image, and event instructor records can show Upload image (optional), Replace image, or Remove image depending on the resource. Create or save the metadata row before uploading a file when the screen requires an ID. Accepted image types in the current components are JPEG, PNG, WebP, and GIF.

After saving a reference value, search for it again and confirm the linked record uses the intended value. A read-only resource has no add or delete control; do not infer that an unsupported reference action is available. Role and administrator-account writes remain superuser-only.