Our package's custom objects are initially set as "private" for external users by default. Community user permission sets provide access to custom objects and their fields, but not to records created by other users (both internal and external).
Within community portals, administrators have the following two options for setting up eSign flows:
- Use our prebuilt components (self-sign and simple-sign).
- Create your own flows using our Apex APIs.
In both cases, admins often use agreement templates to enable community users to initiate or participate in eSign flows. For this to work, community users need read-only access to agreement templates and related resources, such as merge and data mapping objects, which are typically created by internal users.
The type of community user license determines how access can be granted:
- Community User Login License: Admins can enable "ViewAll" for agreement templates and merge/data mapping objects through the community user profile to grant access.
- Community User Login PLUS License and Partner Community User License: Enabling "ViewAll" access via the profile isn't possible. Admins need to use roles-based sharing rules to provide access.