Nembl
Admin Guide
B2B Collaboration
B2B Requests

B2B Requests

The B2B Requests page is the unified list of every cross-Company request your Company is involved in — both inbound (others submitted to you) and outbound (you submitted to others). Use it to triage, track, and audit cross-Company work.

Open from B2B → Requests.

For internal-only requests (within your Company), use the standard Requests view.

Tabs: Inbound / Outbound

The page splits cleanly into two tabs:

Inbound

Requests sent to your Company by partners. Each row shows:

  • Source Company
  • Target service / offering
  • Title
  • Submitted at
  • globalStatus (PENDING / ACCEPTED / IN_PROGRESS / COMPLETED / REJECTED / CANCELLED)
  • Local owner (the team / inbox handling it on your side)

Inbound requests behave like internal requests once accepted — they flow through your workflows and your responsibility model. The B2B view just adds visibility on the source-Company side and SLA tracking against the offering's SLA Policy if one is bound.

Outbound

Requests your Company submitted to partners. Each row shows:

  • Target Company
  • Their service / offering
  • Title
  • Submitted at
  • globalStatus (as reported by the partner)
  • Local submitter (who in your Company sent it)

Outbound requests are read-mostly from your side — the partner Company runs them through their workflow. You see the status updates they push and any messages they send.

Filtering

  • Search — text-matches title, source / target Company, service name
  • Direction — Inbound only / Outbound only / Both
  • Status — multi-select on globalStatus
  • Partner Company — narrow to one specific partner
  • Date range — submitted at

Detail view

Click into any request to open its detail page, which shows:

  • Full request metadata (title, fields submitted, attachments)
  • Conversation thread between the two Companies' teams
  • Workflow timeline (visible to both Companies; each side sees only their portion)
  • SLA timer (if applicable)
  • Status history with timestamps

The audit trail for cross-Company actions is mirrored in both Companies' B2B Audit Trails so neither side can tamper with the other's record.

Cross-Company actions you can take

From the detail view, depending on direction:

  • Inbound: Accept (moves to your inbox / workflow), Reject (with reason), Comment, Update status, Mark complete
  • Outbound: Comment, Cancel (notifies the partner), Resubmit (creates a new request linked to this one), Acknowledge a status update

Status changes are pushed to the partner Company's instance via the cross-Company event bus. Latency is typically sub-second on the same region; cross-region setups see a few seconds.

Privacy

  • The partner Company sees only their view of the request — submitted fields, conversation messages they're a party to, and globalStatus updates
  • Internal phase activity (your team's tasks, internal comments, auto-generated notifications) is not visible to the partner
  • Use the explicit "External update" composer to send a message both sides see

Related

B2B RegistryConnections