You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/setup-vendor.md
+42Lines changed: 42 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,48 @@ they keep access to those versions beyond the specified date. If you want to rem
95
95
This is useful if your customers buy a license from you for a certain timeframe e.g. a full year and therefore should get
96
96
access to all versions that are released within that year.
97
97
98
+
## Using vendor bundles to manage customer access to packages
99
+
100
+
Vendor bundles allow you to group packages and grant multiple customers access to the same packages. Instead of having to
101
+
grant customers access to every package individually, you grant them access to a vendor bundle, and they will automatically
102
+
receive access to all packages in the bundle. Adding additional packages to that bundle will then automatically grant
103
+
all customers with access to the bundle access to these packages as well.
104
+
105
+
Vendor bundles can be managed on the Vendor Bundles section from the Vendor tab, and they can be assigned to customers on the bundle section of a customer.
106
+
107
+
Vendor bundles can also be created and customer access can be granted via our API using our [API client](https://github.com/packagist/private-packagist-api-client) with the following code snippet:
108
+
109
+
```
110
+
<?php
111
+
112
+
require_once __DIR__ . '/vendor/autoload.php';
113
+
114
+
$customerId = 42;
115
+
116
+
$client = new \PrivatePackagist\ApiClient\Client();
0 commit comments