Government of Manipur

Help & user manuals

The SuperAdmin is the only role not scoped to a single department. You create departments, appoint their first Admin, manage the campaign calendar, and can act anywhere records exist.

You see
Every department's records
You alone can
Create departments & their first Admin
Dashboard shows
Cross-department activity breakdown

1 Sign in

There is no self-registration on this portal — every account, including yours, is issued by the previous SuperAdmin or seeded at setup.

  1. Open /account/login — the Departmental login link in the header.

  2. Enter your official email address and password, then select Sign in.

  3. First time in? You'll land on Change your password and must set a password of at least 12 characters before doing anything else. Five failed attempts locks the account for a period — contact whoever issued it if that happens.

2 Set up a new department

Every event record belongs to a department, so this is usually the first thing a SuperAdmin does for a new participant in the abhiyan.

  1. Go to Departments in the top nav, then New department.

  2. Fill in the department's identity:

    Department code — short and permanent, e.g. HEALTH. Used internally, not shown to the public.

    Department name, Short name, Parent department (for a sub-office), About, Website URL, Contact email — the public-facing profile.

  3. Set two behavioural switches before saving:

    Pickup window (days) — a submitted record left unreviewed this long becomes visible to any Admin in the department, not only the Operator's own supervisor. Defaults to 3 days.

    Allow self-approval — only meant for a department with a single Admin and no one else to check their work. Leave this off wherever there's more than one reviewer.

  4. Select Save department. The department now exists but has no members yet — it can't do anything until it has an Admin.

3 Appoint the department's first Admin

Only a SuperAdmin can create the first Admin of a department — from then on, that Admin creates their own Operators.

  1. Open the department from Departments, scroll to Admins, and use the form there — no separate page.

  2. Enter the officer's Full name, Email, and Designation, then select Add admin.

  3. The portal generates a temporary password and shows it once, on screen, right after you submit. It is not emailed and cannot be retrieved later — copy it and hand it to the officer over a secure channel before you navigate away.

  4. The officer must change that password at their first sign-in, same as you did. If an Admin leaves the post, come back to this list and select Deactivate next to their name — accounts are never deleted, only deactivated, so the record trail stays intact.

4 Manage campaigns and programmes

A campaign (like Seva Sankalp Utsav/Abhiyan, 2026 itself) is the umbrella; a programme is one named activity inside it that a department can tag its events with.

  1. Go to Campaigns, then either open an existing one or select New campaign and set its Code, Name, Starts on / Ends on dates, and Active flag.

  2. Inside a campaign, the Programmes panel lists every named programme under it. Add one with Programme name, an optional Suggested nodal department, and a Sort order for display.

  3. Programmes are toggled active or inactive, never deleted — events already tagged with one keep that link permanently, even after the programme is retired.

5 Grant permissions beyond the defaults

Every account starts with a sensible default permission set for its role. You can extend an individual account further, up to the ceiling its role is allowed to hold.

  1. From Operators, select Permissions next to the account (works for Admin memberships too, via the same page reached from a department's Admins list).

  2. Tick or clear individual permissions. A box is disabled if the target role isn't allowed to hold it at all, or if you don't hold it yourself — you can never grant a permission you don't have.

  3. The one deliberately unusual case: Approve and publish is allowed for an Operator, not just an Admin — but it isn't on by default for anyone. A department can grant it to a trusted Operator who needs to publish without waiting on an Admin.

6 Read your dashboard

Your /manage dashboard is the only one that aggregates across every department.

  1. The four stat cards — Draft Returned Published — total every department's events at once. Select one to jump to that filtered list.

  2. Department activity ranks departments by total events recorded, with a bar split between what's published and what's still pending — the fastest way to see who needs a nudge.

  3. Recent activity is a live feed of every submit, return, approve, publish and unpublish across the whole portal, newest first.

You're the reviewer for one department (or more, if you hold more than one membership). You add Operators, review what they submit, and decide what goes public.

You see
Your own department's records only
You alone can
Create Operators & review submissions
Dashboard shows
What's waiting on you right now

1 First sign-in

  1. A SuperAdmin creates your account and hands you a one-time temporary password — there's no self-registration.

  2. Go to /account/login, sign in with that password, then set your own on the Change your password screen that follows automatically (12 characters minimum).

2 Add an Operator to your department

Operators are the ones who actually record events day to day — you'll usually want at least one before anything gets submitted to you.

  1. Go to Operators, then New operator.

  2. Choose which Department / supervising Admin membership they'll report to (yours, if you only hold one), then fill in Full name, Email, and Designation.

  3. Select Create operator account. Copy the temporary password shown on screen — it's shown exactly once — and pass it to them securely. They set their own password at first sign-in, same as you did.

  4. Every Operator must report to an Admin — that's what makes their submissions land in your queue rather than a shared pool. If they leave, select Deactivate next to their name in the Operators list; the account and its history stay on record.

3 Review a submitted event

When an Operator submits, it lands in your queue — visible on your dashboard under Needs your attention the moment it happens.

  1. From the dashboard, select Review → next to the record, or find it via Manage events.

  2. Read the description, dates, attendance figures, and check the photos — every image the Operator uploaded is on this page, along with any YouTube or Vimeo link they added.

  3. Satisfied? Select Approve. Something needs fixing? Write what, in Return with remarks, then select Return — it goes back to the Operator as a Returned draft they can edit and resubmit.

One rule the system enforces for you

You can't approve a record you created and submitted yourself, unless you're the department's only Admin and Allow self-approval was switched on when the department was set up. It's a written-in-the-database rule, not just a UI hint — a second pair of eyes is expected wherever there is one to have.

4 Publish, and unpublish if needed

  1. An Approved record isn't public yet — open it and select Publish to put it on the public site immediately, or leave it approved if the release should wait.

  2. To take a live record down, open it and use Unpublish with reason — the reason is kept as part of the record's history, and the record can always be republished later from the same page.

5 Grant permissions to an Operator

  1. From the Operators list, select Permissions next to their name.

  2. You can only grant what you hold yourself, and only within what an Operator is allowed to hold at all. The one worth knowing: Approve and publish can be handed to a trusted Operator so they don't have to wait on you for routine records — it isn't on by default, so this is the only way they get it.

6 Keep your department profile current

Your department's About, Website URL, and Contact email appear on its public profile — worth a look whenever they change.

  1. Open your department from Departments, edit the fields under Department details, and select Save department.

7 Read your dashboard

  1. Stat cards, Needs your attention, and Recent activity are all scoped to your own department — nothing else is mixed in.

  2. The active campaign panel shows how many of your department's events fall under the current abhiyan, if one is running.

You're the one closest to the ground — you turn an actual event into a record: the details, the photographs, and (unless you've been trusted with more) a submission for your Admin to check.

You see
Your own department's records
You always can
Create, edit and submit drafts
Sometimes granted
Approve and publish, if your Admin extends it

1 First sign-in

  1. Your Admin creates your account and gives you a one-time temporary password.

  2. Sign in at /account/login, then set your own password (12 characters minimum) on the screen that follows.

2 Record a new event

Nothing here is visible to the public until it's submitted and approved — saving is always safe.

  1. Go to Manage events, then New event.

  2. Fill in what happened:

    Event title, Description, Venue, Category, District.

    Campaign and Programme — tag the event to Seva Sankalp Utsav/Abhiyan, 2026 and the specific programme it was held under, if it applies.

    Starts at / Ends at, and Organised with for any partner department or agency.

    Attendance — total, male, and female counts.

  3. Tick Consent has been obtained for identifiable individuals appearing in any media for this event — required before you can submit, not before you can save.

  4. Select Save draft. It's saved under Draft and only you and your department's Admins can see it.

3 Add photos and video

  1. Open the draft and use Upload photo to add images — the first one you mark as cover is what represents the event on the public listing.

  2. For video, paste a YouTube or Vimeo link and select Add video link — video is never uploaded directly to the portal, only linked, unless your department has switched on direct upload.

4 Submit for approval

  1. When the record is complete, open it and select Submit for approval.

  2. It moves to and lands in your supervising Admin's queue. You can no longer edit it while it's in this state.

5 Track what happens next

  1. Open the record any time to see its status and full history at the bottom of the page — every submit, return, approve, and publish, with who and when.

  2. Came back as Returned? The remarks explain what to fix. Edit the draft and submit it again — there's no limit on how many times a record can go around.

6 If you've been granted approval rights

Not the default for anyone — but an Admin can extend Approve and publish to a trusted Operator so routine records don't have to wait.

  1. If it's been granted to you, Approve and Publish appear on your own submitted records the same way they do for an Admin.

  2. One thing that never changes: you still can't approve a record you created yourself, unless your department's Admin has switched on self-approval for a single-Admin department — and that flag is about Admins, so in practice an Operator's own submissions still need a second person.

Reference: what each status means

The same states apply to every event record, whichever role is looking at it.

StatusMeaning
DraftBeing written. Visible only inside the department.
Waiting for an Admin (or an Operator with Approve rights) to review it.
ReturnedSent back with remarks. Editable again, ready to resubmit.
ApprovedReviewed and cleared, but not yet on the public site.
PublishedLive on the public site — visible to anyone, no login required.
UnpublishedWas public, taken down with a recorded reason. Can be republished.
RoleDefault authority
SuperAdminEverything, everywhere — the only role that spans departments.
AdminFull control of one department: Operators, review, publish, department profile.
OperatorCreate, edit and submit their own drafts; approve/publish only if granted.