Front-end Administrator Guide

1. Front Administration Overview

Explains what the front administration area is, who should use it, and how it differs from the private ClassiCore owner back end.

What this area is for

The front administration area is the day-to-day operating workspace for trusted website administrators. It allows authorized staff to manage member access, listings, moderation, verification, plan assignments, media rules, support accounts, featured profiles, and other operational settings without entering the private WordPress ClassiCore Control Center.

This area is intended for people who actively run the website: moderators, membership administrators, support leads, verification reviewers, or another person the owner has specifically authorized.

The owner back end remains the place for licensing, SMTP credentials, deep branding, plugin configuration, and other platform-level controls. The front admin is for operating the live community.

Use this area when

• An administrator needs to review or approve member content.
• A trusted staff member needs to assign a plan, verify a profile, feature a member, or manage a support account.
• The owner wants to delegate daily operations without giving someone full WordPress Administrator access.
• An administrator needs a mobile-friendly or front-end workspace that matches the public site.

How to use it safely

1. Confirm the person has a legitimate operational role and understands the site rules, privacy policy, and escalation process.
2. Give them the narrowest role that allows the required tasks. Do not use a full owner account for ordinary moderation work.
3. Have the administrator sign in through their own named account. Shared administrator passwords make accountability impossible.
4. Test what the role can see before handing over access. Confirm it cannot reach owner-only licensing, SMTP, financial, or WordPress plugin settings unless intentionally authorized.
5. Review access whenever a staff member changes duties or leaves the team.

Common controls and what they mean

2. Quick Actions

The left-side shortcuts that let an administrator move between public member tools and administration tools quickly.

What this area is for

Quick Actions keeps the most-used areas in one predictable menu. It lets administrators see the site from a member’s perspective while still reaching the operational controls needed for their role.

These links are especially useful when an administrator is testing a change. They can configure a setting, then immediately browse listings, open their own test listing, check messages, or review the account area.

Use this area when

• You need to move quickly between administration and the live member experience.
• You are testing whether a plan, media limit, tap rule, or listing setting behaves correctly.
• You need to open the inbox, account area, saved listings, or posting form without navigating through the public menu.

How to use it safely

1. Use Browse listings to see the same listing results members see.
2. Use Post a listing only when creating a real authorized listing or a clearly identified test/support listing.
3. Use My listings to inspect listings owned by the administrator’s account.
4. Use Saved listings to review items the account has bookmarked.
5. Use My account to manage the administrator’s own front-end profile and account preferences.
6. Use Inbox to review the administrator account’s conversations and system notices.
7. Use Admin settings or Front-end app settings only for tasks within the administrator’s assigned authority.

Common controls and what they mean

3. Admin Settings Dashboard

The card-based dashboard that opens each operational setting group.

What this area is for

The Admin Settings dashboard is the front administrator’s control panel. Each card represents one area of responsibility, such as listing limits, moderation, uploads, plans, verification, or safety.

The cards are separated so administrators can change one operational rule without searching through a long settings form. This also makes it easier for the owner to explain which cards a staff role is allowed to use.

Use this area when

• You need to change an operational rule that affects members or listings.
• You need to review a queue, assign a plan, feature a profile, or configure safety accounts.
• You are diagnosing why a member can or cannot upload, renew, publish, tap, or access a feature.

How to use it safely

1. Read the description on the card before opening it. Confirm the card matches the task you are trying to complete.
2. Write down the current value before changing it.
3. Change one setting group at a time and save it.
4. Test the result with an appropriate test account and membership plan.
5. Record significant operational changes so other administrators know what changed and why.
6. Escalate owner-level decisions such as pricing promises, licensing, SMTP, legal policy, or major monetization changes.

Common controls and what they mean

4. Front-end App Settings

Controls the behaviour and presentation of the member-facing ClassiCore application from the front administration area.

What this area is for

Front-end App Settings is used for controls that shape how the live ClassiCore experience behaves for members and authorized administrators. The exact options can vary by vertical, edition, and installed extensions.

This area may include navigation behaviour, browse modes, member controls, mobile presentation, account tools, or other front-end application options that do not require access to the private owner back end.

Use this area when

• The front-end experience behaves differently from the intended workflow.
• An administrator needs to enable or disable an operational member-facing option.
• You are testing mobile navigation, front-end account tools, browse behaviour, or another app-level control.

How to use it safely

1. Review the setting description and identify which members, plans, or devices it affects.
2. Take a screenshot or write down the original configuration.
3. Make the smallest required change.
4. Test while logged in as an ordinary member, a paid member where applicable, and an administrator.
5. Test on both desktop and mobile before considering the change complete.
6. Escalate visual branding, licensing, SMTP, or platform-level changes to the owner back end.

Common controls and what they mean

5. Listing Limits

Sets how many active listings or profiles each membership level may have.

What this area is for

Listing Limits controls the maximum number of active listings a member can maintain under each plan. On a Personals site, the normal limit may be one profile per account. Classifieds or Rentals may allow several active listings.

The limit is a membership rule, not a billing charge by itself. It tells ClassiCore when to allow another listing and when to ask the member to remove, expire, or upgrade.

Use this area when

• You are defining what Free, Bronze, Silver, Gold, or another plan includes.
• A member can create too many listings or is incorrectly blocked from creating one.
• You are adding a new membership level or changing a product promise.

How to use it safely

1. Confirm the public plan description and owner-approved entitlement for each membership level.
2. Enter the allowed number of active listings for each plan.
3. Decide whether drafts, pending listings, expired listings, or trashed listings count toward the limit in the current configuration.
4. Save the settings and test with an account on each affected plan.
5. Confirm the error or upgrade message is understandable when the limit is reached.
6. Update pricing and help pages if the allowance changed.

Common controls and what they mean

6. Listing Renewals

Controls how many times a listing can be renewed on each membership level.

What this area is for

Listing Renewals determines whether a member can extend or reactivate the same listing after its active period ends, and how many times that action is allowed.

A renewal is not automatically the same as a new purchase. Depending on the plan design, it may simply refresh the listing period or may require a valid paid entitlement.

Use this area when

• You are deciding whether members may extend an existing listing.
• A member sees a renewal option unexpectedly or cannot renew when they should.
• You are changing plan durations or listing expiry rules.

How to use it safely

1. Confirm whether renewals are part of each plan promise.
2. Enter the allowed renewal count for every plan. Use zero when renewals should be disabled.
3. Confirm what duration a renewal adds and whether the renewed period begins immediately or from expiry.
4. Test the renewal flow with an expired test listing.
5. Confirm plan access remains valid and that WooCommerce or another entitlement system does not contradict the renewal rule.
6. Update member-facing wording if the policy changes.

Common controls and what they mean

7. Listing Expiry

Sets how long listings remain active for each membership level.

What this area is for

Listing Expiry controls the active lifespan of a listing or profile. When the configured period ends, ClassiCore can expire, hide, or require action on the record according to the site workflow.

This value is separate from the member’s account and may also be separate from the plan’s billing period. The distinction matters when diagnosing access problems.

Use this area when

• You are defining how long each plan keeps a listing active.
• A listing expired earlier or later than expected.
• You are changing plan durations, renewals, or account-entitlement rules.

How to use it safely

1. Confirm the intended listing lifetime for each plan.
2. Enter the duration using the unit required by the form.
3. Confirm how “Never” or unlimited expiry is represented before using it.
4. Test a short-duration test listing or use a staging site to confirm the expiry action.
5. Check what members see before and after expiry and whether they can renew, edit, or republish.
6. Keep the public plan wording aligned with the actual duration.

Common controls and what they mean

8. Plan Durations

Defines how long each paid or free membership level remains active.

What this area is for

Plan Durations controls the access period attached to each membership level, such as a seven-day free plan, a fourteen-day Bronze plan, a thirty-day Silver plan, or a ninety-day Gold plan.

The plan duration controls entitlement. It should be reviewed alongside listing expiry, WooCommerce mapping, and the public product description.

Use this area when

• You are setting up or changing membership periods.
• A member’s plan ended at the wrong time.
• You are adding a new plan or mapping a new WooCommerce product.

How to use it safely

1. Confirm the owner-approved duration for each plan and whether the period begins at assignment, purchase, activation, or another event.
2. Enter the duration for every active membership level.
3. Check the plan-to-product mapping before testing a purchase.
4. Assign a plan to a test account and confirm the calculated start and end dates.
5. Test what happens when the plan ends: access removal, downgrade, listing expiry, or another action.
6. Update pricing pages, receipts, and help documentation when the duration changes.

Common controls and what they mean

9. Listing Moderation

Determines whether new listings require administrator approval before becoming public.

What this area is for

Listing Moderation controls the publication gate. When approval is required, new or edited listings enter a pending queue rather than appearing immediately.

This is a core safety and quality control for sites that need to review photos, descriptions, prohibited content, fraud indicators, or category accuracy.

Use this area when

• You want all new listings reviewed before publication.
• You are adjusting moderation requirements by plan or listing type.
• A member says their listing is pending or appeared without review.

How to use it safely

1. Decide which listings require approval: all new listings, selected plans, selected categories, or edited listings where supported.
2. Enable the appropriate moderation rule.
3. Publish a test listing and confirm it enters the correct queue.
4. Review the listing against the site rules, not personal preference.
5. Approve, reject, request changes, or escalate according to the moderation policy.
6. Record serious decisions and notify the member in clear, neutral language.

Common controls and what they mean

10. Video Uploads

Chooses which membership levels may attach video to listings.

What this area is for

Video Uploads controls plan-based permission to add video to a listing or profile. It is an entitlement and storage decision as well as a member-facing feature.

Video can improve engagement, but it requires stronger moderation, larger storage, more bandwidth, and clear file restrictions.

Use this area when

• You are deciding which plans include listing video.
• A member can or cannot upload video unexpectedly.
• You are responding to storage, moderation, or performance concerns.

How to use it safely

1. Confirm which plans are supposed to include video uploads.
2. Enable video only for those plans.
3. Check the allowed file types, maximum file size, quantity, and duration in the relevant media settings.
4. Test an allowed and disallowed upload using a plan-specific test account.
5. Confirm moderation and front-end playback on desktop and mobile.
6. Review server storage and retention policies regularly.

Common controls and what they mean

11. Image Uploads

Sets how many listing images each membership level may have.

What this area is for

Image Uploads defines the gallery allowance for each plan. It can be used to create meaningful differences between free and paid membership levels.

The number applies to listing or profile media according to the current vertical. It should be coordinated with full-resolution visibility, moderation, storage, and public plan wording.

Use this area when

• You are defining photo allowances by plan.
• A member reaches an image limit too early or can upload too many images.
• You are changing a paid-plan benefit.

How to use it safely

1. Confirm the image allowance promised for every plan.
2. Enter the maximum number of listing images for each membership level.
3. Clarify whether the primary image counts toward the limit.
4. Test uploading, replacing, reordering, and deleting images with plan-specific test accounts.
5. Confirm image moderation, cropping, compression, and front-end display.
6. Update plan comparisons when the allowance changes.

Common controls and what they mean

12. Message Media Limits

Controls how many images or videos a member may send to the same recipient within a rolling time window.

What this area is for

Message Media Limits is an anti-spam and safety control for private conversations. It limits how much media one member can send to the same recipient during a defined period.

The rolling window means the system looks back over a period of time rather than resetting only at midnight.

Use this area when

• You are reducing media spam or harassment.
• A legitimate user reaches the media limit unexpectedly.
• You are defining different messaging allowances by plan.

How to use it safely

1. Choose a reasonable image and video allowance for each plan.
2. Set or confirm the rolling time window used by the limit.
3. Test sending media up to the limit and one item beyond it.
4. Confirm the sender receives a clear message explaining when they can send again.
5. Check whether administrator or support accounts need special handling.
6. Monitor abuse reports and adjust only with owner-approved policy.

Common controls and what they mean

13. Tap Settings

Sets the tap cooldown and provides an administrator reset tool for tap limits.

What this area is for

Tap Settings controls how frequently one member can send the quick-interest action to another member. A cooldown prevents repeated tapping from becoming spam or pressure.

The administrator reset is for support cases, testing, or a confirmed technical problem. It should not be used to bypass the normal rule casually.

Use this area when

• You are setting the site-wide tap cooldown.
• A user reports that a tap remains blocked after the cooldown should have ended.
• You need to reset tap state for a legitimate support or test case.

How to use it safely

1. Confirm the owner-approved cooldown period.
2. Enter the duration and save it.
3. Test sending a tap, attempting another tap during the cooldown, and sending again after the period.
4. Confirm the recipient receives the expected notification or inbox event.
5. Use the reset tool only after verifying the accounts and reason.
6. Document repeated resets if they indicate abuse or a technical defect.

Common controls and what they mean

14. Media & Watermark

Adds a simple text watermark to listing images and controls related media presentation.

What this area is for

Media & Watermark can brand public listing images with a site name or other approved text. It may help discourage casual reuse and identify the source platform.

A watermark is a presentation and deterrence feature. It is not strong copyright enforcement and does not make an image impossible to copy.

Use this area when

• You want public listing images to carry approved site branding.
• You are changing watermark text or presentation.
• Users report that a watermark is unreadable, intrusive, or missing.

How to use it safely

1. Confirm the exact owner-approved watermark text.
2. Choose placement, opacity, size, or other available options conservatively.
3. Upload or select a test image with light and dark areas.
4. Confirm the watermark is readable without covering faces, product details, or essential listing content.
5. Test whether the watermark applies only to new images or also regenerates existing versions.
6. Keep an unwatermarked original where the platform’s storage and policy require it.

Common controls and what they mean

15. Plan / WooCommerce Mapping

Links each ClassiCore membership plan to the correct WooCommerce product.

What this area is for

Plan / WooCommerce Mapping tells ClassiCore which membership entitlement should be granted when a particular WooCommerce product is purchased.

This connection is critical. The product handles the commercial transaction, while ClassiCore applies the resulting access and duration.

Use this area when

• You are connecting a new membership product.
• A successful purchase assigns the wrong plan or no plan.
• You are replacing, renaming, or retiring a WooCommerce product.

How to use it safely

1. Confirm the exact WooCommerce product intended for each ClassiCore plan.
2. Map one product to the matching plan and avoid ambiguous duplicate mappings.
3. Save the mapping.
4. Complete a controlled test purchase using a test customer and suitable payment method or staging environment.
5. Confirm the order status, assigned plan, start date, end date, and member-facing access.
6. Confirm cancellations, refunds, failed orders, or expired access behave according to the owner’s policy.
7. Document product IDs and mappings before replacing or deleting a product.

Common controls and what they mean

16. User Plan Manager

Manually assigns, changes, extends, or clears a member’s ClassiCore plan.

What this area is for

User Plan Manager is the administrator tool for account-specific entitlement changes. It is useful for support corrections, complimentary access, migration, testing, or an approved exception.

Manual assignment can override the normal purchase path, so every change should have a clear reason.

Use this area when

• A paid order succeeded but the plan was not assigned correctly.
• The owner approves complimentary or promotional access.
• You are migrating a member from another system.
• You need to remove an incorrect or expired entitlement.

How to use it safely

1. Locate the correct member using their username, email, or account identifier.
2. Confirm the current plan, source of access, dates, and related order before changing anything.
3. Select the approved replacement plan or clear the plan if appropriate.
4. Enter or confirm the effective and expiry dates.
5. Save and verify the account from the member-facing side.
6. Record the reason, approving person, and related order or support ticket.
7. Check whether an automated WooCommerce process could later overwrite the manual change.

Common controls and what they mean

17. Featured Profiles

Highlights selected profiles, pins sticky profiles, and controls date headers on Personals browse pages.

What this area is for

Featured Profiles lets administrators promote selected member, support, sponsor, or official profiles within browse results. Sticky behaviour can keep selected profiles near the top.

Because featuring changes visibility and can have commercial value, the site should have a clear policy for who qualifies and how long the placement lasts.

Use this area when

• You are promoting a paid featured benefit.
• You need an official support profile to remain easy to find.
• You are managing a sponsored or editorial profile placement.
• You are changing date-header behaviour on Personals browse pages.

How to use it safely

1. Confirm the profile is eligible and that the placement is owner-approved.
2. Select the profile and choose featured, sticky, or the available placement type.
3. Enter an end date where supported so temporary promotion does not remain forever.
4. Preview browse ordering with ordinary, featured, sticky, support, and sponsored profiles.
5. Confirm the placement is clearly labeled where advertising or consumer rules require it.
6. Remove or renew the placement when the approved period ends.

Common controls and what they mean

18. Profile Verification

Reviews live selfie verification requests, approves genuine matches, and revokes verification when necessary.

What this area is for

Profile Verification helps confirm that a member can produce a current live selfie that reasonably matches the person represented by the profile. It is an authenticity signal, not a complete identity or background check.

Administrators review requests, approve or decline them, and may revoke a badge if the profile later changes, evidence is invalid, or the verification was granted incorrectly.

Use this area when

• A new verification request enters the review queue.
• A member asks about a pending or declined request.
• A verified profile changes its main identity photos or is reported for impersonation.
• You need to revoke an earlier approval.

How to use it safely

1. Open the request in a private environment where unauthorized people cannot see the selfie.
2. Confirm the submission appears live and current according to the platform’s capture method and timestamp or overlay.
3. Compare the verification image with the profile’s public identity photos. Look for a reasonable match, not perfection.
4. Check for obvious replay, screenshot, deepfake, edited-image, or impersonation indicators within the limits of the available evidence.
5. Approve, decline, request a new submission, or escalate according to the verification policy.
6. Do not claim that approval proves legal identity, age, criminal history, or safety unless the product truly performs those checks.
7. Revoke verification when the badge is no longer justified and document the reason.

Common controls and what they mean

19. Admin / Support Safety

Reserves official usernames, defines support accounts, and protects trusted support profiles from ordinary member controls.

What this area is for

Admin / Support Safety establishes which accounts are official platform representatives and prevents members from impersonating reserved identities.

It can also protect legitimate support profiles from being blocked when the site needs them to remain available for safety, onboarding, or customer assistance.

Use this area when

• You are creating or updating an official help, moderation, safety, or administrator profile.
• You need to reserve usernames such as Support, Admin, Safety, or the site name.
• A support account is being hidden or blocked in a way that prevents required platform contact.

How to use it safely

1. Define the exact official usernames and naming pattern approved by the owner.
2. Reserve those names so ordinary members cannot register confusingly similar official identities where the feature supports it.
3. Assign the approved accounts as support or administrator profiles.
4. Enable only the protections required for the account’s role.
5. Make official profiles visually clear and explain what they can and cannot do.
6. Review the list when staff change and immediately remove former staff access.
7. Test messaging, profile visibility, blocking rules, and browse placement with an ordinary member account.

Common controls and what they mean

20. Discovery View

Opens the optional image-first profile discovery extension and its operational settings.

What this area is for

Discovery View provides an app-style grid, Browse and Live modes, filters, location scopes, maps, taps, profile opening, guest discovery, featured ordering, and sponsored placements according to the installed configuration.

The front-admin link gives authorized administrators a direct route to the operational Discovery View controls without requiring access to unrelated owner settings.

Use this area when

• Live mode is showing members who are not currently online.
• Browse filters, location scopes, map behaviour, taps, or clear/reset controls need adjustment or testing.
• You are managing guest browsing, featured profiles, support visibility, or sponsored tiles.
• You need to verify mobile layout or member conversion prompts.

How to use it safely

1. Open Discovery View Settings from the front admin.
2. Confirm which tile details, filters, and location options are intended to be visible.
3. Test Browse and Live separately. Live should use the platform’s configured online definition.
4. Test local-radius, selected-country, and global scopes where enabled.
5. Test Use My Location with permission allowed, denied, and previously blocked.
6. Test map markers, profile opening, Back to Results, Clear, Close Map, and return-to-home behaviour.
7. Test taps and cooldowns with normal and support accounts.
8. Review guest-visible data and conversion prompts as privacy decisions.
9. Check mobile alignment, active-filter chips, scrolling, and sponsored content.

Common controls and what they mean

21. Viewer Insights

Manages the optional viewer-history extension, including access, privacy behaviour, and plan entitlement.

What this area is for

Viewer Insights records profile views and can show members who viewed them, whether viewing is identified or anonymous, and which plan is entitled to use the feature.

The front-admin card also shows whether the extension is enabled and whether its licence or access status is active.

Use this area when

• You are configuring which plans receive viewer history.
• A member cannot access Viewer Insights or sees unexpected viewer information.
• You are reviewing anonymous or revealed viewing behaviour and privacy controls.
• You need to confirm the add-on is active after installation or migration.

How to use it safely

1. Confirm the extension status shows enabled and active.
2. Open Configure and review plan access.
3. Decide which viewing events are identified, anonymous, hidden, or revealed according to the owner’s privacy policy.
4. Test with two controlled member accounts: view one profile, then confirm the expected record appears.
5. Test quick messaging, hiding, clearing, or other viewer-record actions where available.
6. Confirm expired or downgraded plans lose access appropriately without exposing unexpected history.
7. Escalate licence activation or installation problems to the owner back end.

Common controls and what they mean

22. Daily Administrator Workflows

Practical routines for handling the most common front-admin responsibilities consistently.

What this area is for

The individual cards explain each control, but administrators also need repeatable routines. A daily workflow reduces missed approvals, inconsistent decisions, and undocumented account changes.

The owner should decide which routines apply, who owns each queue, and what must be escalated.

Use this area when

• You are training a new administrator.
• You are assigning responsibilities across moderation, verification, support, and membership administration.
• You want predictable response times and clear accountability.

How to use it safely

1. At the start of the shift, review pending listings, verification requests, reports, and support messages assigned to the role.
2. Handle urgent safety matters first, then time-sensitive paid-access problems, then ordinary moderation and support.
3. Use written policies for approvals, rejections, verification, featuring, and plan exceptions.
4. Document manual plan assignments, revoked verification, serious moderation, protected accounts, and unusual resets.
5. Test operational setting changes with dedicated test accounts before announcing completion.
6. At the end of the shift, record unresolved cases and hand them to the next responsible person or owner.
7. Escalate legal requests, credible threats, child-safety concerns, payment disputes, licence issues, SMTP problems, and major policy changes.

Common controls and what they mean

Administrator operating checklist

• Every administrator uses an individual account.
• Two-factor authentication is enabled where available.
• Roles are limited to the smallest practical access level.
• Pending listings and verification requests have a named owner and response target.
• Manual plan changes are documented with a reason and approval.
• WooCommerce mapping is changed only by authorized senior administrators.
• Official support accounts are current and former staff access has been removed.
• Featured placements have a reason and, where appropriate, an end date.
• Discovery View is tested for privacy, location, Live mode, maps, and mobile behaviour.
• Viewer Insights behaviour matches the published privacy explanation.
• Major changes are tested with ordinary member accounts, not only administrators.
• Unresolved safety, legal, payment, or owner-level issues are escalated promptly.