QQivo

Time, calendar and capacity settings

  • Org → General: organization name; the organization's address (below); date format (six formats, live preview) applied everywhere; "Workdays start on" — the first workday of the week, which anchors every roadmap column; "Week 1 of the year" (First 4-day week / ISO 8601, week containing Jan 1, or first full week); and "Default plannable hours per week" (below).
  • Your organization's address — the name your organization lives under, and the part of the URL that comes after qivo.io/app/: everything you open reads qivo.io/app/acme/… (§ Links you can share). It is made from the organization's name when the organization is created (lowercased, spaces and punctuation turned into single hyphens) and it is unique across every organization, so if the name you chose is already in use you are given the next free variant — acme, then acme-2. Two organizations called the same thing therefore never collide. Five things are worth knowing before you change it:
    • Renaming the organization does not change the address. They are separate on purpose: a name is something you read, an address is something people have saved. Change the address only when you mean to.
    • The change is immediate, and it is not forwarded. Every link anyone has bookmarked or shared stops working the moment you save — there is no redirect from the old address to the new one.
    • The address you leave becomes free straight away, and another organization can take it. This is deliberate: if old addresses were reserved for ever, an organization could quietly hoard names simply by renaming itself over and over.
    • Some addresses are not available. If the one you want is already taken, or is a word reserved for the product itself (docs, pricing, admin, settings and about a hundred others), saving tells you which of the two it was and you pick another. There is no "check availability" button, because an address held by an organization you cannot see would always look free — saving is how you find out.
    • The change is recorded. Moving the address writes a line into the organization's activity naming both the old address and the new one and who made the change, so a colleague who finds their bookmark dead can see what happened without asking.

    Only an organization admin can change the address.

    Because a released address can be taken by somebody else, the app watches for it on your behalf: if an address you have used before opens a different organization than it did last time, Qivo stops before showing you anything and tells you whose organization it is now. You confirm once, and it doesn't ask again.

  • Plannable hours per week — the one capacity number the app plans against: the team strip's 100%, auto-fit's weekly budget and the delay projection's walking speed. It is the time someone has for planned project work — their week minus meetings, email and other overhead — so it is deliberately smaller than a contracted work week, and it is always a whole number of hours (1–168): planning to the half hour was precision nobody had. It belongs to the person, so it follows them into every team and project they work in, and two people in the same team can have different weeks. Two places set it:
    • Org → General → "Default plannable hours per week" (32 out of the box) — the week a new user starts on. Changing it never rewrites anyone who already has hours.
    • The person's own hours, an inline h/wk field on their row in Org → Users — guests have one too, further down the same page, and theirs is the week this organization plans them at — or on their row in a team's member list. An org admin can set anyone's; a team's leader can set the hours of the people in their own team, without being an admin. It is not self-service: ordinary users can't raise or lower their own planning capacity, and where the field is read-only its tooltip names who can change it.
  • Team (Settings → Organization → Teams → the team you lead): name and icon; max attachment size (1–50 MB); the stale threshold; the auto-archive threshold (days a Done task rests before it archives itself, §9); the delay-tracking default for new projects; and the team's member list with a per-person Leader checkbox (the leader runs the team — membership itself grants no access, see §12) and each member's plannable week.
  • Org → Labels: the organization's shared label list — rename a label and it renames everywhere, click its dot to cycle colors, and deletion warns with a live "used on N tasks" count. Anyone in the organization can put a label on a task; curating the list takes an org admin, a project lead, or a user role on some project.
  • Identity: teams and projects each take an icon or emoji from a searchable Linear-style picker. The Icons tab holds around a hundred line icons, which take a tint colour (a palette plus a custom picker); the Emojis tab holds the full standard emoji set — roughly 1,700 of them in the nine usual groups, every country flag included — and emoji keep their own colours, so there is nothing to tint. At that size search is the way in: type what the thing is rather than hunting for it, and synonyms are matched too, so "deploy" finds the rocket and "defect" finds the bug. Sub-projects are text-only — just a name, no icon or abbreviation — and there are no per-project or per-milestone identity colors to pick: on task surfaces, the status colors (§7) are the color language, so nothing decorative competes with them.

✦ What sets this apart — Calendar-week configuration is first-class: your org defines what "W32" means and which day a week starts on, and the entire roadmap, week numbering and planning grid follow. Most tools plan by dates and leave week semantics to guesswork.