Help

Help›Ask Tightly›Inbox

Inbox

Reviewed Oct 29, 2026

View as Markdown
Words
TierEvery tier
SeatA seat that can write
WhereInbox, the second row of the rail, under Home

The question this page answers ​

What is waiting on my decision, and what does yes do? Inbox groups pending decisions assigned to you by kind, ranked by money. Read each row's consequence before deciding.

Conversation notifications open the permitted record thread and referenced revision. Read/unread uses its receipt. Replying or resolving a thread does not decide a business action.

What you see ​

Inbox, the head and the table, marked 1 to 2.
  1. The head, Inbox, with its three tabs, Decisions, Notifications and History, and the pin.
  2. The table, grouped by kind, ranked by money then newest first.

Tabs show Decisions with its pending count, Notifications, Conversations and History.

Decisions has four columns: What, From, Waiting and Amount. Hover Waiting for the arrival date. Amount reads Not priced when unstated and totals each group and the table. Rows are grouped by kind and ranked by money, then newest first.

Open a row for its business details, subject link, consequence and decision buttons. It opens beside the list or in a drawer on narrow screens. On wide screens the biggest row opens automatically.

Email attachments and uploaded business documents open in Ask Tightly for field review. Resolve missing fields, then explicitly apply. Results link to the affected record or an order document awaiting review.

Notifications lists what has arrived for you, with Mark all read while any are unread.

Conversations lists discussions you can access. Search or filter their status to find the conversation you need.

History lists Item, Recorded decision, Decided and Reported outcome. Filter by Approved / marked done or Rejected / dismissed; use Previous and Next to browse. Open a row for its facts. Missing outcomes read No outcome recorded.

The kinds ​

KindYesNoWhat yes does
Parked runApproveRejectResumes the parked run; rejecting cancels it
ApprovalApproveRejectYour decision is recorded; a run waiting on it resumes or cancels
Finance approvalApproveReturn for changesLets a Buy approver confirm the order, or returns it with a note; Reassign hands it on
Planning review taskOpen planning reviewReturn in the working planOpens the exact submitted revision for review; a returned plan opens its author’s current draft
TaskMark doneDismissMarks it done; nothing else runs
Commitment amendmentApprove & applyRejectApplies the amendment as a new receipted version of the commitment
Autonomy promotionApprove & promoteDeclineRaises the commitment to the offered rung
Plan changeApprove & applyRejectApplies the change to the working plan; publishing stays with a person
Markdown proposalAcceptRejectRecords the accepted depth; the price change stays with you
Tightly Connect reorderAcceptRejectRecords the accepted reorder; placing it with the account stays with you
Email importReview importDecline in reviewOpens the saved proposal in Ask Tightly; review and correct its fields before explicitly applying it
Sell-out fileImportNot this fileLands the file as that account's week; their grade re-reads
Supplier updateApproveIgnoreWrites the change to the order, then marks the update approved
Account claimAcceptDismissVersions the account's line through the book's one decision route

Accepting an Approval for a price drop seen at your store records that price as the product's price from the day it was seen. It writes no price anywhere.

The Sell-out file, Supplier update and Account claim rows arrive from Ask Tightly reading your mail. A colleague asking you to sign a commitment off arrives as a row of its own kind, with Acknowledge and Decline:

Sign-off requested

Signing off happens in the room; this row is the ask.

A Finance approval shows the order's totals, payments, budget, blockers and changes; only finance approvers and admins see company cash. A batch has Approve all. Approving does not confirm.

An Additional buy request row does not open here: it opens Work the Buy on its commitment, with Review supply in the row. A kind the page does not know yet shows in plain words with Approve and Reject, and its yes reads Your decision is recorded.

Trading follow-ups ​

A trading follow-up task shows its due date and decision. Trading tasks also show the selected week, comparison week and view. Open Trading scope or Open Sales scope returns to the saved selection. Before Mark done or Dismiss, you may enter a Reported outcome (optional). That note stays in History.

Marking done records the assignee's decision. It does not verify that the action ran or caused a business outcome. The History drawer names this basis Reported evidence.

What to do ​

  1. Open a row and read its consequence.
  2. Choose its offered action.
  3. Wait for the decision, then read the recorded outcome.

You decide only rows assigned to you; a row assigned to someone else, or already decided, is refused. Deciding needs a seat that can edit.

When it is empty or failed ​

Nothing waiting.

Your inbox could not be read just now.

A failed read offers Try again in the head. A decision the server refused prints its sentence where the two verbs stood, or

Not recorded, nothing changed.

where it gave none, and the row stays pending. On the Notifications tab an empty list reads Nothing new. and a failed one Notifications could not be read just now. History reads No recorded decisions in this view. when empty, or Could not load history. with Try again after a failed read.

Order and stock exceptions stay in their operational review queue. Assignment, comments and snoozing preserve their history; a snoozed exception remains unresolved. Inbox Approve and Reject do not act on these exceptions.