Skip to content

THE PLATFORM

One platform. Many connected decisions.

Explore how Viganium brings operations, people, client relationships and team communication into a clearer operating picture.

01Operations & Delivery

Work, without the chaos.

Give every project a clearer path from assignment to review.

Connect projects, tasks, workflows, Q Tasks and support tickets. Keep ownership, deadlines, comments and changes in context, while leaders see where decisions or reviews are needed.

How the work moves

  1. Create & assign
  2. Work in levels
  3. Review
  4. Done

What it keeps on record

  • Every assignment, status change and review keeps its history.
  • Missed SLA deadlines are recorded as violations, with their details.

Modules

  • Projects

    Client or internal projects with an owner, members, status, priority and dates. A project takes new work while it is in progress or in Support — never once it is completed, cancelled or archived.

  • Tasks

    Assigned to a person, a whole department or a workflow, with comments, files, an activity history and reviews.

  • Workflows

    Work passed through people in levels: everyone on a level works at once, and the next level starts when they have all finished.

  • Q Tasks

    Each department's numbered pool of work, in the order its leader sets.

  • Leaders Tasks

    One department leader asks another for something, with everything a task carries.

  • Tickets & SLA

    Client requests routed to the responsible department, each with two clocks — a View SLA and an Assignment SLA — plus warnings and a full history.

02People & Working Time

Built around people, not just processes.

Bring structure to working time without losing the human context.

Manage shifts, actual worked time, leave, overtime, remote-work approvals, short-day reviews, penalties counted in days and a points wallet. Keep the rules traceable and give employees a way to review what applies to them.

How the work moves

  1. Roster
  2. Shift
  3. Worked time
  4. Review

What it keeps on record

  • Working time, breaks and inactivity are recorded separately.
  • Employees see their own attendance, requests and penalties.

Modules

  • Shifts & roster

    Shift definitions, a roster for each person and day, and company holidays.

  • Attendance & presence

    One Regular Shift per work date, with breaks. The desktop agent (Windows and Mac) reports activity state and screen lock during a shift — never what was typed. Optional Free Shifts after it are recorded separately and never count toward required hours or overtime.

  • Daily hours

    Each day is judged once against the hours its shift owes. A day more than an hour short goes to an administrator to decide.

  • Leave, overtime & remote work

    Leave requests and balances, overtime that is asked for and approved, and remote work with two approvals in order — a leader, then an administrator.

  • Penalties & objections

    Penalties are counted in days and follow written rules. Employees can object, and an administrator decides — never on their own case.

  • Points wallet

    Points an administrator grants, with a full ledger of every movement, spent on rewards: cancelling a penalty of a quarter, half or whole day, or one more day of annual leave.

03Client Trust & Quality of Service

Accountability you can actually see.

Good service depends on clarity, not memory.

Keep each client, its contacts and its projects in one record. Track ticket responsiveness, status changes, assignment and resolution histories. Let clients participate through their own portal, while keeping internal records separate and permissioned.

How the work moves

  1. Request
  2. Viewed
  3. Assigned
  4. Resolved

What it keeps on record

  • Status, assignment and resolution histories stay with the ticket.
  • What a client sees is decided by the system, not by memory.

Modules

  • Clients

    A client is always a company, with its contacts, its projects and its portal sign-ins in one place.

  • Two SLA clocks

    A View SLA and an Assignment SLA on every ticket, with deadlines fixed when it is created.

  • Client portal

    Clients sign in to their own portal to follow their tickets and their projects' tasks. Their accounts are kept apart from staff accounts.

  • Change requests

    A conversation both ways until a request is decided, and work created from it once accepted.

  • Complaints

    A formal channel for clients to raise a concern about the work on their projects, routed to the people who review it.

  • SLA compliance report

    For any period: tickets created, tickets assigned on time, open violations and the compliance rate.

04Communication & Meetings

Keep context closer to the work.

The platform is more than a task board.

Internal mail, chat, announcements, meetings, questions and notifications keep conversations next to the work they are about — on the web and on the phone.

How the work moves

  1. Notify
  2. Discuss
  3. Meet
  4. Ask & answer

What it keeps on record

  • Notices reach each person in their own language.
  • An audit trail records changes across the platform.

Modules

  • Internal mail & chat

    Mail that never leaves the system, and chat with any colleague.

  • Announcements & meetings

    News to everyone or chosen teams, a meeting calendar, and booking links that people outside the company use to pick a time.

  • Questions

    One question to departments and people together — a written answer, or one or several choices — with an optional deadline. Each person answers once and sees only their own answer.

  • Notifications

    Notices in English and Arabic, in each person’s own language, with desktop push and email.

  • Viganium Team (Android)

    The employee app keeps essential work within reach: tasks and tickets, mail, chat, meetings and leave requests.

05Files & Sites

Files that stay with the work.

Private until you share it.

Everyone has a drive of their own. Share a folder with a colleague or the whole company, file it under the client or project it is about, or send a client's contacts a link that stops when you say so. And publish a static website from files you upload.

How the work moves

  1. Upload
  2. Organize
  3. Share
  4. Publish

What it keeps on record

  • Whatever goes to the Trash is hidden from everyone it was shared with, and its links stop.
  • An administrator picks who may publish sites, by department or by name.

Modules

  • Viganium Drive

    A private drive for everyone — folders inside folders, files of any kind — shared with any colleague or the whole company, to view or to edit.

  • Client & project files

    A folder or file can be about a client or a project, and the client's or project's own page lists everything about it that you may open.

  • Sites

    A static website in a folder of its own, at its own address. Upload files, a whole folder or a .zip, edit pages in the browser, and download the site back as a .zip.

HOW IT FITS TOGETHER

Separate doors. One connected system.

One API and one database serve every part. Each door opens only what its people need: staff sign in to one Admin, each with one role, and clients sign in to their own portal with accounts kept apart.

  • Admin

    Operations: people, projects, tasks, tickets, shifts, communication, files and reports.

  • Client portal

    Separate client accounts that see only their own requests and projects.

  • Viganium Team

    The Android app for employees and leaders, limited to a fixed set of actions.

  • Desktop agent

    Windows and Mac. Reports activity state and screen lock during a shift.

  • Shared links

    Files and folders shared outside the company open without signing in — until their last day, or until they are stopped.

  • Sites

    Static websites published from the Admin, each at its own address, and kept out of search engines unless you choose otherwise.

Built to be accountable

  • Scoped roles and permissions

    People see what their role and their departments allow — and nothing else.

  • An audit trail

    Changes that matter are recorded with who made them and when.

  • Arabic and English

    Every surface works in both languages, right-to-left and left-to-right.

Scope, plainly

What Viganium Connect is — and what it is not presented as today:

  • It is not a finance, payroll or accounting system: there are no invoices, payments or salaries in it, and penalties are counted in days, not money.
  • It does not monitor servers or websites, and it has no integrations API for outside systems today.
  • The mobile app is Android-only today, and shifts start and end on the web or desktop, not on the phone.
  • Every company is different: fit and any customization are agreed before adoption.

Questions about the platform

Does the platform include finance?

No. Viganium Connect runs operations, people, clients and communication; it holds no invoices, payments, payroll or accounting. Clients are kept as companies with their contacts and projects, and penalties are counted in days.

How is employee working time handled?

Schedules and configured daily hours are considered alongside started shifts, breaks and activity state. Actual worked hours are distinguished from rest and inactivity, and the system includes approvals and review paths.

Is there a client portal?

Yes. Authorized client accounts can follow supported tickets and project-level information and submit change requests. Internal notes and private employee data remain restricted.

Can the platform connect with other systems?

Not today: there is no integrations API for outside systems. If your company needs one, that belongs in the first conversation — it may point to a custom build.

More questions about getting started

See it against your own operations.

A discovery call explores whether Viganium Connect fits the way your company works, or whether a custom system makes more sense.

  • Use Viganium Connect

    Explore the existing platform and discuss how it could fit your company.

  • Build Your Own System

    Start with your processes, constraints and goals. Design the right software around them.