Admin Work Guide
This guide explains what each admin role should do, what every panel section is for, what the visible columns mean, and which actions should be handled carefully. Use it before giving someone access or before changing products, coupons, resources, affiliates, or users.
Access Levels
| Level | Work | Limits |
|---|---|---|
| Superadmin | Owns the whole panel. Can manage admins, products, bundles, content, resources, coupons, affiliates, reviews, orders, analytics, and users. | Use only for trusted owners. A superadmin can disable other admins and change access. |
| Admin | Runs operations. Can manage products, bundles, blogs, resources, coupons, affiliates, reviews, orders, analytics, and users. | Cannot create/update/disable admins unless promoted to superadmin. |
| Editor | Maintains public content: products, bundles, blogs, resources, and reviews. | Cannot delete records. Should edit and publish, not remove important data. |
| Support | Helps customers with orders, users, and review-related support. | No product/content/coupon/affiliate control unless department access also allows it. |
Departments
| Department | Extra Work |
|---|---|
| Marketing | Analytics, blogs, resources, reviews, and affiliates. Best for SEO/content/social/partner work. |
| Finance | Orders, analytics, coupons, affiliate referrals, and payouts. Best for revenue, coupon control, and payout records. |
| Technology | Products, bundles, file delivery, thumbnails, and technical product setup. |
Dashboard
The Dashboard is the first health check for the store.
| Area / Column | Meaning | What admin should do |
|---|---|---|
| India Revenue | Total local currency revenue visible to the current role. | Use it to monitor Razorpay/India sales trend. |
| International Revenue | International-buyer revenue visible to the current role. | Use it to monitor Razorpay international sales trends; orders are settled in INR. |
| Orders | Total orders count. | If unusually low/high, check Orders and Analytics. |
| Users | Total registered users visible to the role. | Use for customer growth and support context. |
| Products | Active product count. | If count is wrong, check product Active switches. |
| Recent Orders | Latest customer purchases. | Confirm successful orders and spot failed/missing delivery issues. |
| Quick Actions | Shortcut buttons for common work. | Only buttons allowed for your role are shown. |
Orders
Orders show customer purchases. Support, finance, admin, and superadmin should use this section for payment and delivery questions.
| Column | Meaning | How to use it |
|---|---|---|
| Date | When the order was created. | Use it to find recent customer payments. |
| Customer email connected to the order. | Use it to match support messages and account records. | |
| Items | Products or bundles purchased. | Confirm what the customer should receive. |
| Amount | Order total and currency. | Compare with gateway receipts if payment is disputed. |
| Status | Payment/order state such as paid, pending, failed, or refunded. | Do not promise delivery until status is paid/verified. |
| Payment ID | Gateway reference from Razorpay, a legacy provider, or an internal payment id. | Use for gateway lookup and reconciliation. |
| Search | Filters visible rows. | Search by email, item, status, or payment id. |
| Prev / Next | Pagination controls. | Move through more orders without loading everything at once. |
Analytics
Analytics shows how customers move through the site. Marketing, finance, admin, and superadmin use this to make store decisions.
| Metric / Panel | Meaning | Admin work |
|---|---|---|
| Pageviews | Total page visits/events tracked. | Check whether SEO/campaign traffic is growing. |
| Sessions | Visitor sessions. | Compare against pageviews to understand repeat browsing. |
| Cart Adds | How often products are added to cart. | Low cart adds can mean weak product pages or pricing. |
| Checkout Starts | How often users begin checkout. | If cart adds are high but checkout starts are low, inspect cart/checkout UX. |
| Wishlist Adds | Saved product activity. | Use this to identify products customers consider but may not buy yet. |
| Top Pages | Most visited URLs. | Improve important pages and request indexing for new public pages. |
| Top Sources | Traffic origins. | Understand which channels are working. |
| Search Demand | Internal search/query signals. | Create products, glossary terms, or blogs for repeated searches. |
| Event Mix | Breakdown of tracked actions. | Use to spot broken funnels or missing tracking. |
Products
Products are single digital items customers can view, save, compare, add to cart, buy, and download after payment.
| Table column | Meaning | What to do |
|---|---|---|
| Name | Public product title. | Keep clear and searchable. It appears on product cards and detail pages. |
| Category | Product grouping such as Automation, SOP, AI, Notion, Productivity. | Controls category pages and filtering. |
| Price | Displayed product price. | Check carefully before publishing. Checkout verifies price server-side. |
| Badge | Small label like Popular, New, Best Value. | Use for merchandising, not for long text. |
| Active | Whether product is public/available. | Turn off for drafts, discontinued products, or broken delivery. |
| Download | Private delivery/file status. | Make sure delivery object exists before selling. |
| Actions | Edit/Delete controls. | Edit updates product. Delete appears only to admin/superadmin. |
Product form fields
| Field | Purpose | Guidance |
|---|---|---|
| ID / Slug | Stable URL identity. | Use lowercase words with hyphens. Do not change after Google indexes unless necessary. |
| Name | Main title. | Make it specific: tool + outcome. |
| Description | Main product summary. | Explain outcome, who it is for, and what it includes. |
| Short Description | Compact card/preview text. | Keep it short and benefit-focused. |
| Full Description | Long detail area. | Add setup details, use cases, and exact contents. |
| Target Audience | Who should buy. | Example: agencies, founders, creators, freelancers. |
| Result / Outcome | What changes after using it. | Write the practical result, not vague promises. |
| Requirements | Tools or accounts needed. | Mention Zapier, Make, n8n, Notion, Airtable, Google Sheets, etc. |
| Workflow Steps | How the system works. | Use one step per line if possible. |
| Tags | Search/filter/SEO helper terms. | Use comma-separated tags that customers would search. |
| FAQs | Product questions and answers. | Use format: Question | Answer. Add practical buyer concerns. |
| Difficulty | Setup complexity. | Beginner, Intermediate, Advanced, or similar. |
| Setup Time | Estimated time to use. | Example: 15 minutes, 1 hour, 1 day. |
| Version / Last Updated | Trust and maintenance info. | Update when files or instructions change. |
| Thumbnail | Public marketing image. | Do not use private download links as images. |
| Download URL/File | Private delivery source. | Use private storage delivery. Do not paste permanent public files. |
Bundles
Bundles group multiple products into a stronger offer. They should feel like a complete operating stack, not a random discount pack.
| Column / Field | Meaning | Admin work |
|---|---|---|
| Name | Bundle title. | Use a clear audience/outcome name. |
| Category | Bundle family. | Helps customers understand the bundle purpose. |
| Price | Current bundle price. | Must be checked carefully before publishing. |
| Original Value | Total separate-product value. | Use to show savings honestly. |
| Inclusions | Products/files included. | List included product IDs one per line where requested. |
| Active | Public availability. | Disable if files are missing or offer is retired. |
| Download | Bundle delivery/file status. | Verify before selling. |
| For Who | Ideal buyer. | Explain who should choose this over a single product. |
| Outcome | Main result. | Describe the business result the bundle creates. |
| Tags / FAQs | SEO and buyer clarity. | Use practical tags and buyer questions. |
| Actions | Edit/Delete controls. | Delete is admin/superadmin only. |
Blog Posts
Blog posts support SEO, customer education, and product discovery.
| Column / Field | Meaning | How to use |
|---|---|---|
| Title | Post title. | Use a clear search-friendly headline. |
| Slug | URL path after /blog/. | Keep stable after publishing. |
| Category | Content category. | Group posts by subject. |
| Status / Published | Whether post is public. | Draft until complete. |
| Views | Tracked post visits. | Use to find strong topics. |
| SEO Title | Google/social title. | Use if different from post title. |
| SEO Description | Meta description. | Summarize value in one short paragraph. |
| Canonical URL | Preferred URL. | Leave empty unless avoiding duplicate content. |
| Tags | Topic keywords. | Use comma-separated terms. |
| Related Product IDs | Products shown with post. | Use product IDs that fit the article. |
| Cluster | SEO topic group. | Assign posts to a Content Cluster when possible. |
| Actions | Edit/Delete controls. | Delete is admin/superadmin only. |
Resources
Resources are SEO/AIO support pages. They help customers and AI/search engines understand MOLVRIX topics.
| Resource type | Columns | Work |
|---|---|---|
| Content Clusters | Name, Slug, Keyword, Active, Actions. | Create topic groups for blog/content strategy. Name is display title, slug is URL, keyword is SEO target, Active controls public visibility. |
| Glossary Terms | Title, Slug, Category, Active, Actions. | Define terms like workflow automation or secure digital delivery. Title is public term, slug is URL, category groups terms, Active controls visibility. |
| Use Cases | Title, Slug, Product Categories, Active, Actions. | Map customer problems to product categories. Categories should match product category slugs such as automation, sop, productivity, notion, ai. |
| Actions | Edit/Delete. | Editors/marketing can create/update. Delete is admin/superadmin only. |
Coupons
Coupons control discounts. They affect revenue, so only trusted finance/marketing/admin users should manage them.
| Column / Field | Meaning | What admin can do |
|---|---|---|
| Code | The customer enters this at checkout. | Use uppercase clear codes. Avoid confusing characters. |
| Type | Discount type, usually percent or fixed amount. | Choose percent for percentage discounts; fixed for exact currency amount. |
| Value | Discount amount. | For percent, value is percentage. For fixed, value is money amount. |
| Used | How many times coupon has been redeemed. | Monitor campaign usage and abuse. |
| Per Customer | Maximum use by one customer. | Use 1 for one-time customer coupons. |
| Expires | Coupon end date. | Set an expiry for campaigns. Empty/no expiry means longer-running coupon if allowed. |
| Active | Whether checkout can accept the coupon. | Turn off to stop usage without deleting history. |
| Actions | Edit/Delete controls. | Edit to change limits/status. Delete only if it should be removed completely; admin/superadmin only. |
Coupon workflow
- Click + New Coupon.
- Enter code, type, value, usage limits, expiry, and active status.
- Test checkout with the coupon before public campaign launch.
- Watch Used and Per Customer during the campaign.
- Disable instead of deleting when a campaign ends and history matters.
Reviews
Reviews are customer feedback shown on product pages after approval.
| Column | Meaning | Admin work |
|---|---|---|
| Product | Product being reviewed. | Check review belongs to the right product. |
| Rating | Customer star score. | Use to understand product quality. |
| Review | Customer written text. | Reject spam, abuse, private data, or irrelevant text. |
| Status | Pending, approved, or rejected. | Approve helpful reviews, reject unsafe/irrelevant reviews. |
| Helpful | Helpful vote count. | Use as a signal of review usefulness. |
| Actions | Approve, reject, or delete depending on role. | Delete only for admin/superadmin. Prefer reject for moderation history. |
Affiliates
Affiliates promote MOLVRIX and earn commission on referred sales.
| Column / Action | Meaning | Admin work |
|---|---|---|
| Name / Email | Affiliate identity. | Use for communication and verification. |
| Status | Pending, active, rejected, or suspended. | Approve good applicants, reject weak/spam applications, suspend risky affiliates. |
| Code | Referral code/link identity. | Generated on approval. Customers or links use it for tracking. |
| Clicks | Referral traffic count. | Monitor traffic quality. |
| Pending | Unpaid commission/referrals. | Finance should verify before payout. |
| Paid | Paid commission total/history. | Use for payout reconciliation. |
| Approve | Makes affiliate active and generates code. | Use after reviewing application quality. |
| Reject | Rejects application. | Use for spam, poor fit, or unclear promotion plan. |
| Suspend | Stops active referral use. | Use for abuse, fraud, or policy issues. |
| Pay | Records payout for unpaid referrals. | Finance should enter method/reference and notes. |
Payout History
| Column | Meaning |
|---|---|
| Date | When payout was recorded. |
| Affiliate | Who was paid. |
| Amount | Payout amount. |
| Method | Razorpay Route, manual bank transfer, UPI, PayPal, or another approved reference. |
| Status | Payout state. |
| Notes | Transaction id, internal note, or proof reference. |
Users and Admin Directory
Users shows admins and access assignments. Only superadmin can add, update, or disable admin access.
| Column / Field | Meaning | How to use |
|---|---|---|
| Total Users | All registered accounts visible to the role. | Use for account base overview. |
| Total Customers | Registered non-admin customer count. | Use for customer growth. |
| Total Admins | Enabled admin/staff accounts. | Review regularly for least-privilege access. |
| Admin account email. | User must already have a MOLVRIX account before assignment. | |
| Name | Admin display name. | Helps identify the team member. |
| Admin Level | support, editor, admin, or superadmin. | Controls broad access level. |
| Admin Role | Department: marketing, technology, or finance. | Adds focused permissions. |
| Joined | When admin access was added. | Use for audit/history. |
| Actions | Edit or disable admin access. | Superadmin only. You cannot disable yourself. |
How to assign admins
- Make sure the person first creates a normal MOLVRIX account.
- Open Users and click + Add / Update Admin.
- Enter the account email.
- Choose Access Level based on trust and work.
- Choose Department based on daily responsibility.
- Save and ask the user to sign out/sign in again if access does not refresh.
| Date | Items | Amount | Status | Payment ID | |
|---|---|---|---|---|---|
| Name | Category | Price | Badge | Active | Download | Actions |
|---|---|---|---|---|---|---|
| Name | Category | Price | Inclusions | Active | Download | Actions |
|---|---|---|---|---|---|---|
| Title | Slug | Category | Status | Views | Actions |
|---|---|---|---|---|---|
| Name | Slug | Keyword | Active | Actions |
|---|---|---|---|---|
| Title | Slug | Category | Active | Actions |
|---|---|---|---|---|
| Title | Slug | Product Categories | Active | Actions |
|---|---|---|---|---|
| Code | Type | Value | Used | Per Customer | Expires | Active | Actions |
|---|---|---|---|---|---|---|---|
| Product | Rating | Review | Status | Helpful | Actions |
|---|---|---|---|---|---|
| Name | Status | Code | Clicks | Pending | Paid | Actions | |
|---|---|---|---|---|---|---|---|
| Date | Affiliate | Amount | Method | Status | Notes |
|---|---|---|---|---|---|
| Load affiliates to view payouts. | |||||
| Name | Admin Level | Admin Role | Joined | Actions | |
|---|---|---|---|---|---|