NowToPrint — Global print marketplaceالمساعدة

Organisation Management

How organisations, profiles, role bindings, membership access, and team membership work in NowToPrint.

docs5 دقيقة قراءةتمت المراجعة 21 أكتوبر 2026

Organisations in NowToPrint are the primary tenant boundary for users, resources, marketplace profiles, membership access, and billing or contract state. A single user can belong to multiple organisations with different role bindings in each.


Organisation profiles

Technical organisation types can still be personal, company, or supplier, but authorization and marketplace behaviour also use profile information:

ProfileDescriptionTypical capability family
BuyerIndividual or company buying printRFQ, quote compare, quote accept, order tracking
SupplierPrint shop or production vendorRFQ inbox, quote create, order lifecycle, supplier capabilities
Broker / AgencyActs on behalf of customersBuyer plus selected supplier workflows
VendorMaterial or equipment vendorFuture vendor marketplace
Service ProviderService supplierFuture service marketplace

Personal account

The initial workspace is created during verified onboarding. Registration or sign-in alone does not grant every business capability. You can subsequently hold memberships in other workspaces with different roles.

Company account (Buyer)

A workspace for a business buying print. Team invitations and actions depend on current permissions, seats and effective access. Naming a company does not verify its identity. Shared organization resources retain their own access and ownership rules.

Supplier account

Print-producer onboarding starts with candidate membership and baseline customer access. Quoting, publishing, production and producer finance actions stay closed until the required review and grants are valid. Separate self-service material/equipment vendor registration is currently closed.

A personal account and its organization memberships are distinct; one person can work in more than one workspace.

Organisation roles

TemplateResponsibility
OwnerOwnership and delegation
AdminTeam setup and permitted operations
OperatorProfile-specific RFQ, quote and order workflows
FinanceAuthorized financial views and operations
ViewerRead access within the permitted scope

Templates expand to canonical organization/profile roles. An organization finance role does not grant platform payment approval, refund, payout release, role administration or entitlement management. Membership, action permissions, effective entitlement and release gates are separate requirements.

See User Roles.

Membership and entitlement relationship

Organization membership establishes the tenant boundary; role permissions and the current effective entitlement snapshot determine each action. Legacy package labels never grant authority.

Your sign-in session proves who you are, but it does not carry organisation permissions. For every protected organisation action, NowToPrint reads your current active membership and role bindings on the server. A removed, inactive, unreadable, or different-organisation membership is denied immediately, even when the browser still has a valid sign-in session.

  • Print Customers begin with baseline purchasing capabilities.
  • Producer Candidates retain baseline customer capabilities while producer actions remain closed.
  • Verified, Expert, and Strategic Producer authority is activated only by the reviewed, time-bounded membership lifecycle.
  • A persisted plan name or visible label cannot override an expired, revoked, tenant-mismatched, or otherwise denied grant.

Creating an Organisation

  1. Open Profile, then Create an organization.
  2. Choose corporate customer, agency or print producer.
  3. Enter a 2–100 character workspace name.
  4. Submit and keep the same attempt if a network result is unclear.
  5. Follow the success continuation/sign-in prompt to install the new context.

This person-level additional-workspace form differs from a platform administrator creating an organization for another owner. It does not bypass review or effective entitlement. The continuation must verify the same person; selecting a browser context alone grants no permissions.

Managing Members

Adding a member

  1. Switch into the correct organization using the sidebar context selector.
  2. Open Teams.
  3. If permission and seat policy allow it, choose Invite member.
  4. Enter the email and select Admin, Operator, Finance or Viewer; send the invitation.

The recipient accepts a pending invitation with the matching verified email. An email is a destination, not the authorization principal. Creating the record does not prove email delivery. Follow the current invitation status instead of relying on a universal seven-day lifetime. Owner is excluded from ordinary invitations.

Changing a role

Teams displays the delegation model and active memberships; it does not currently offer a generic member-row role editor. Transfer ownership is a separate action among eligible current members with server authorization and security checks. Use the authorized management flow for other role corrections.

Removing a member

Do not assume a generic Remove menu exists on Teams. Ask the authorized administrator to use the applicable membership-management flow. Removed or inactive membership cannot authorize protected organization actions merely because the person's sign-in session is still valid.

Add-on and legacy package note

Older add-on package language is no longer the canonical access model:

Legacy phraseCurrent model
Supplier PackSupplier capability family
MIS PackSupplier order lifecycle / production capabilities
CRM PackCustomer/lead permissions and future capability set

This keeps commercial packaging and authorization decisions on the same SSOT.


Previous: ← User Roles | Next: First Order →

هل كانت هذه المقالة مفيدة؟

مقالات ذات صلة

Ask AI Assistant