Step 5: Manager Approval

← Back to Step 4: Create/Update Fabric Tokens | Skip to Step 6: Send Fabric Tokens →

Why manager approval matters

Before fabric token data goes on the blockchain, a manager reviews it for accuracy.

This is the four-eyes principle: one person creates the token, a second person verifies it. This catches mistakes, typos, and calculation errors before they're permanent.

You're checking: Is the data accurate and complete?

Who needs to approve?

If you're a User: You create/update/send tokens, then wait for manager approval.

If you're a Manager: You review and approve (or reject) token requests before they go live.

Don't have a manager set up yet? Email support@aware.com with their name and email. We'll add them to your account.

How to review token requests

Go to: Manage > Create Token Requests

You'll see all pending requests waiting for approval.

Review the token

Click the eye icon in the "Action" column to view the full token details (the "digital twin").

Check carefully:

• Fabric composition adds up to 100%?

• Total weight correct?

• Yarn tokens linked properly (if applicable)?

• Total material weight = total fabric weight?

• Sustainability claims accurate?

• Self Validation documents complete?

• No typos in fabric specifications or customer names?

Approve or reject

Click the report icon in the "Action" column.

Option 1: Approve

Everything looks good? Click "Approve Aware™ Token Request"

The token goes live and can be sent to the customer.

Option 2: Reject

Something's wrong? Click "Reject Aware™ Token Request"

Good rejection notes:

• "Total fabric weight shows 1,000 kg but should be 1,050 kg"

• "Composition shows 110% total (should be 100%)"

• "Missing yarn token from ABC Spinning Mill"

• "Self Validation invoice is for different batch (check batch number)"

Bad rejection notes:

• "Wrong" (what's wrong?)

• "Fix this" (fix what?)

• "Check the data" (which data?)

The clearer you are, the faster they can correct it.

What happens after approval?

Once approved, the token is written to the blockchain (permanent record). The User can now send it to the customer.

Once it's on the blockchain, you can't edit it. That's why careful review matters.

What happens after rejection?

The User receives a notification with your rejection reason. They fix the error and resubmit. You'll review it again.

You've completed Step 5 ✓

Next: Step 6: Send Fabric Tokens to Customers →

The final step - delivering verified fabric data to your customers.

Need help? Click the "?" icon in the platform or email support@aware.com

← Back to Step 4: Create/Update Tokens | Skip to Step 6: Send Tokens →