Choosing Preferences

You can customize preferences for Collaborative Lifecycle for Dashboard.

  1. From the menu at the upper-right corner, click Preferences .
  2. Choose your settings for the following preference:

    Preference Description
    Credentials Credentials used inside the app to apply rules and visibility on the content. They also determine the location of new objects.

    Select from the list the credentials (access role, organization, collaborative space) you want to use. You can choose from the credentials assigned to you on the current 3DEXPERIENCE platform.

    Note: If the organization is the same for all your credentials, it is not displayed.

    By default, the credentials defined as the default ones for the user in 3DSpace are used. If the dashboard app is removed from a dashboard and added again, the preferences are reset and the default credentials are used again.

    3DEXPERIENCE Platform

    Platform currently used inside the app to manage stored content.

    On the cloud, you can choose among all the platforms available for the connected user.

    Important: If there is only one available platform, then this preference is not available.

    For more information about content management when switching platforms in a multi-platform cloud environment, see Switching Between Cloud Platforms.

    Tip: Hover over the icon in the widget header to display the current platform. You can double-click the icon to open the widget preferences and choose another platform. For more information, see Select a Platform for your Widget.

    Important: The collaborative space and organization of new revisions are not defined by Credentials preference. When you create a revision, it automatically uses the same collaborative space and organization of the revised object. This keeps all the revisions of the object in a same branch shared with the same people. However, the owner of the new revision is the one used for the session.

    Recommendation: Keep the same collaborative space and organization for all the revisions of a branch, even if you can move the new revision afterward.

  3. Click Save.