Partium offers the possibility to create groups of users, typically your customers, who access different portions of the data
All master data which is imported into the Partium systems, as well as user accesses, is arranged in organizations and suborganizations.
Organizations in Partium
An organization is mainly a logic identifier for an entity. Let's assume ACME Corporation is a company selling industrial machines and/or machine parts. "ACME" is then the organization.
When setting up Partium, your master data (Bill of Materials, catalog structure, parts, etc.) will be associated to "ACME". When enabling access to individual users to that data to find parts, those individual users will be associated to "ACME". This association of data on one hand and of users on the other, makes the search for parts specific to the business of ACME alone.
Sub-organizations
Following the example of ACME Corporation, it is very common that when offering the capability to find parts in ACME's catalog, ACME wants each customer (and their users) to access only the portion of the catalog that is relevant to them. A similar example would be that ACME is a conglomerate composed of different businesses, each managing a portion of the catalog. In that case, creating sub-groups of the data and users is convenient.
Let's assume ACME has three customers: ClientA, ClientB, and ClientC, each bought different machines from ACME:
MachineX | MachineY | MachineZ | |
ClientA | ✅ | ✅ | |
ClientB | ✅ | ✅ | |
ClientC | ✅ |
When setting up Partium, it is possible to associate only the data for MachineX (BoM and parts details) to ClientA and ClientB, leaving ClientC without visibility to that information. In addition, the entire master data can be associated to ACME employees which are users who need access to information of all the machines).
Requirements for setting up access groups
When ingesting data into Partium's systems, you'll need to arrange the following information:
- Parent Organization: this will identity your company, which has the highest level grouping that gives the broader access.
- Suborganizations: names to identify each of them.
- Find App Users: identifiers (typically by an email address) and the group they belong to.
- Agent Portal Users: identifiers and the groups they should support.
- Machines: identifiers of the machines that should be accessible by each group.
- Parts: identifiers of the parts that should be accessible by each group. If the Bill of Materials is also provided, then the part to machine association is available and the accessibility will be defined by the machines. If a part is shared by multiple machines, it is then accessible if at least one machine is accessible to the corresponding user.
In case of questions, our Customer Success team will promptly support you.