Direct Answer: How to Enable Private Plans for a Plan Type in OnePlan
To enable private plans for a plan type in OnePlan, an administrator goes to the General settings area > Plan Types tab, opens the plan type edit menu, goes to the security tab, turns on the private plans setting, and selects Save. Once private plans are on for a plan type, plan owners of that type can make plans private, so that most plan information is available only to the users and teams in the plan’s Shared With access.
What This Article Covers: Enabling Private Plans
This article explains how an administrator turns on private plans for a plan type in OnePlan, what to decide before turning it on, how private plans behave across the product, and where private plan restrictions are not enforced.
What you will accomplish By the end of this article, you will be able to enable private plans for a plan type, understand how private plans are enforced or masked in OnePlan, and identify external reports, integrations, and connections you need to review.
For a full explanation of how private plans work, see Private Plans in OnePlan - Overview
Before You Begin: Enabling Private Plans
Make sure you have the following:
- Access to the General settings area in the OnePlan configuration pages. See How Do I Access the Admin Settings.
- An existing plan type. To create one, see Create and Update Plan Types.
- A decision on whether plans of this type should be private from the start. If possible, plan owners should make a plan private when they create it, before connecting its schedule to other plans or adding subplans.
- A review of any OData datasets, external reports, integrations, and Microsoft Teams or SharePoint connections that use OnePlan data. See Where Private Plans Are Not Enforced below.
Why This Matters: Enabling Private Plans
Controlled Visibility
Private plans are turned on by plan type. Plan owners of that type can then restrict a plan so that its information is available only to the users and teams in its Shared With access. This keeps sensitive work, such as confidential initiatives, restructuring, or executive projects, visible only to the people who need it.
Private Plan Access Takes Precedence
Private plan access takes precedence over general system permissions. View All Plans, Edit All Plans, and Administrative access do not necessarily provide access to the contents of a private plan. For more on how private plan access fits with other permissions, see OnePlan Plan Permission Hierarchy.
Where Private Plans Are Enforced or Masked in OnePlan
Some features must continue to work with private plans. In those areas, OnePlan hides identifying information and displays the Plan ID in place of the plan name. Users without access generally cannot find or view the plan.
- Resource Plan — Resource Managers without access can still see existing demand, but the plan name is hidden, demand cannot be edited or replaced, new assignments cannot be created, and Plan Details cannot be opened. Adding the Resource Manager to Shared With lets them contribute.
- Plans and plan relationships — Private plans can remain in hierarchies and lookups. Users without access see the Plan ID instead of the name, and the relationship does not grant access.
- My Work — Assigned users with Plan My Work Only or higher permissions still see their assignments. Resource Managers or delegates without access see masked information.
- Timesheets — Assigned users with access can find work, add time, and submit. Approvers without access can still approve or reject, but plan and work item information is masked.
- Notifications and Automations — Recipients without private plan access are excluded before notifications are sent.
- Dashboards — Users without access do not normally see the plan in dashboard data. Related plan lookups show the Plan ID.
- Modeler, Comments, and the Home Page — People without access do not see private plans or their data.
Where Private Plans Are Not Enforced
Private plan restrictions apply within OnePlan. They do not automatically restrict information that is distributed outside the plan’s direct access controls:
- OData reporting — Datasets can include private plan information unless you exclude private plans from the dataset configuration.
- External integrations — Integrations can send or receive private plan information unless filters are configured. Organizations can filter private plans by plan type to build separate datasets and adjust integrations to meet their requirements.
- Microsoft Teams and SharePoint — Making a plan private does not change permissions already granted in those systems.
- Schedule connections and subplans — If a plan is made private after its schedule was connected to another plan, information already shared remains in the connected schedule until you remove the connection.
- Resource Teams — Team members receive access through the team assignment. Because team membership may be managed outside the plan, the users with access can change over time.
Important: Private plans restrict access to plan information within the application. Do not treat them as a way to revoke information that has already been distributed to external systems, reports, connected schedules, or externally managed repositories.
Note: Review external reports and integrations before enabling private plans for a plan type that holds sensitive plans.
Step-by-Step: Enabling Private Plans for a Plan Type in OnePlan
Task: Open the Plan Type Settings
- Go to the OnePlan configuration pages.
- Select General, then select the Plan Types tab.
- Select the Edit Icon for the Plan Type you want to make private
### Task: Turn On Private Plans for the Plan Type
- Select the Security tab
- Turn on the private plans setting by clicking Enable Private Plans for this plan type
- Select Save.
—
Frequently Asked Questions: Enabling Private Plans
Q: Does View All Plans or Administrative access let me see a private plan in OnePlan? A: Not necessarily. In OnePlan, private plan access takes precedence over general system permissions. View All Plans, Edit All Plans, and Administrative access do not necessarily provide access to the contents of a private plan.
Q: Where are private plan permissions enforced in OnePlan? A: In OnePlan, private plan permissions are enforced or masked in Resource Plan, plan relationships, My Work, Timesheets, Notifications, Automations, Dashboards, Modeler, Comments, and the Home Page. Where a feature must still reference the plan, the Plan ID is displayed instead of the plan name.
Q: Are private plans hidden in OData, external reports, and integrations? A: No, not automatically. In OnePlan, private plan permissions apply only inside the product. OData datasets and integrations can include private plan information unless you configure filters, and permissions in Microsoft Teams and SharePoint are managed in those systems. Organizations can filter private plans by plan type to build separate datasets and adjust integrations to meet their requirements.
Q: What happens if a plan is made private after its schedule is connected to another plan in OnePlan? A: In OnePlan, information already shared through schedule connections or subplan relationships is not automatically removed. Review and remove the applicable schedule connections if connected users should no longer have access.
What to Do Next: Enabling Private Plans
Understand private plans:
Make plans private:
Configure related settings:
Review related concepts:
Comments
0 comments
Please sign in to leave a comment.