Visibility controls

Share policies are how you control what data each customer can see. Every active connection has a share policy that determines which products are visible and at what level of detail.

​

The principle: default deny

LinkXG operates on a default-deny basis. If you do not explicitly share something, the customer cannot see it. This means:

• Customers only see products you have included in the share policy
• Customers only see fields allowed by the visibility package you selected
• Your upstream suppliers are obfuscated by default

You are always in control.

---

​

Visibility packages

Instead of configuring individual fields, you select a visibility package that bundles related fields into meaningful disclosure levels. Standard is the default for new connections. It provides enough information for most business purposes without exposing sensitive details.

---

​

Configuring a share policy

Go to Connections, select a customer, and select Share policy.

​

Product scope

Choose which products to share: If you select “All products”, new products you add will automatically be shared with this customer.

​

Visibility package

Select the package that matches your disclosure intent. See the table above for what each package includes.

​

Field overrides

For fine-tuning, you can override specific fields within your chosen package:

• Reveal a field that the package would normally hide
• Hide a field that the package would normally show

Overrides are limited to a defined set of fields to keep policies manageable.

​

Upstream visibility

By default, your own suppliers (the inputs to your products) appear to customers as obfuscated references like “Upstream Supplier U-1842”. You can choose to:

• Keep obfuscated (default) — Customers see that upstream suppliers exist but not who they are
• Reveal specific suppliers — Explicitly identify particular upstream companies

Revealing upstream suppliers is an active choice. You would typically do this only when you have a specific reason, such as demonstrating a particular certification or origin.

---

​

How obfuscation works

When a customer views one of your products, they may see inputs from your own suppliers. By default, these upstream suppliers are protected: What the customer sees:

• “Upstream Supplier U-1842” (a pseudonym, not the real name)
• Country of origin (e.g., Germany)
• Certification presence (e.g., ISO 9001 ✓)
• Contribution type and quantity bands

What the customer does not see:

• The supplier’s legal name
• Specific location (city, address)
• Documents that might reveal identity

The pseudonym is stable for this customer — they will always see the same “U-1842” reference for the same supplier. But different customers get different pseudonyms, preventing them from cross-referencing your supply chain.

---

​

Revealing upstream suppliers

If you want a customer to see the identity of one of your upstream suppliers, you can create an upstream upgrade. Go to the share policy, find the upstream supplier in question, and select Reveal identity. You can choose what to reveal:

• Identity — The supplier’s real company name
• Location — Full address details
• Certifications — Access to certification documents

Upstream upgrades can have an expiry date if you only want to reveal the information temporarily.

​

The propagation rule

You cannot share more than you received. If your own supplier has obfuscated their upstream sources to you, you cannot reveal them to your customer — because you do not know who they are. This creates a trust chain where each company in the value chain controls their own upstream visibility.

---

​

Making changes

You can update a share policy at any time:

• Add or remove products from scope
• Change the visibility package
• Adjust field overrides
• Reveal or re-obfuscate upstream suppliers

Changes take effect immediately for new data access. Previously shared snapshots are preserved for audit — you can always prove what was visible at a given point in time.

---

​

Audit trail

Every access to your shared data is logged. Go to a connection’s Activity tab to see:

• When the customer accessed your data
• Which products they viewed
• What fields were returned (based on the policy at that time)

This audit trail supports compliance reporting and lets you demonstrate exactly what was shared with whom.

---

​

Common questions

What is the default share policy for new connections? New connections use the Standard visibility package with All products in scope. You can change this immediately after accepting the connection or at any time afterwards. Can I have different policies for different products with the same customer? The share policy applies to the connection as a whole. If you need different visibility for different products, you can use field overrides or consider whether those products should be in separate categories with different sharing rules. What happens if I reduce visibility after sharing data? The customer immediately loses access to fields or products you have removed. They can no longer see that data. However, audit records of past access are preserved. Can a customer request more visibility? Customers can request upstream identity reveals through the platform. You will see these requests in your Action Centre and can approve or decline them.

---

​

Next steps