Document Access
The intent of providing document access in PTC FlexPLM Vendor Portal is to enable collaboration between internal users and vendor portal users in the appropriate context with relevant safeguards.
The use cases supported include the following:
• Generic documents that should be accessible to all users. For example, Reference documents or Training Documents
• Documents created and managed by Vendor, accessible to internal users and Vendor
• Documents that are context specific and shared within the context, between Vendor and internal users or between internal users and all users with access to the product. For example, documents associated to the specification
• Documents that are shared internally and not any Vendor portal user.
To support these use cases various capabilities are enabled in PTC FlexPLM that can be further configured or controlled through settings.
The basic use cases that are supported are as follows:
1. Vendors create documents—Provided appropriate document type level access, Vendors can create new documents.
2. Vendor search documents—Given appropriate type level access, Vendors can search for documents where the logged in user is set as the creator or for all documents belonging to types designated as Open Types For more information, see
Document Security.
3. Vendors update documents—Provided appropriate document type level access, Vendors can update documents that were created by the logged in user. Additionally, a Vendor User can also update other documents shared with them based on type permissions and context.
4. Vendors view documents in the appropriate search context—Vendor access to documents in the Document library using search functionality whether in the Document Library search, Header search, Version Reference attributes chooser search, Document References or Described By references.
Search limits access to document instances based on the following:
◦ Type level policy access controls user access to the document.
◦ Creator—The Vendor user created the document
◦ Open Types—The Document type is configured as OpenTypes.DOCUMENT property for the Vendor. Certain Document Types in the Document Type hierarchy can be configured to be designated as an Open Type. For such types, only Type Manager access is used to validate user access and no additional Vendor Portal access rules (contextual or non-contextual) apply to regulate access.
|
|
This is subject to change in a future release.
|
5. Vendors view documents in other contexts—There are several scenarios where Vendors can review documents either by searching or navigating to them based on the relevant context such as Product or Material or others where the logged in Vendor is associated as a Source or Supplier.
These scenarios include:
◦ Documents associated with a Specification, where logged in Vendor is the Source.
◦ Documents associated with a Material Supplier or Material Color, where logged in Vendor is the Supplier.
◦ Documents associated with a Sample, where logged in Vendor is the Source.
◦ Documents associated to an RFQ Request or Order Confirmation, where logged in Vendor is the Source.
◦ Documents associated to a Vendor (Supplier) associated with which the logged in Vendor user is associated.
