Skip to content

faqs-projects.md

Latest commit

 

History

History
76 lines (51 loc) · 3.49 KB

faqs-projects.md

File metadata and controls

76 lines (51 loc) · 3.49 KB
copyright
years
2022, 2025
lastupdated 2025-04-30
keywords project access, project, project cost, project estimate, project users
subcollection secure-enterprise
content-type faq

{{site.data.keyword.attribute-definition-list}}

FAQ about projects

{: #project-faqs}

FAQs for {{site.data.keyword.cloud}} projects might include questions about support options, configurations, access to projects, and cost estimation. {: shortdesc}

What are {{site.data.keyword.cloud_notm}} projects?

{: #project-log-issue} {: faq} {: support}

As an enterprise, you use projects to ensure that the configuration of your deployable architecture is always compliant, cost effective, and secure. Projects are a named collection of configurations that are used to manage related resources and Infrastructure as Code (IaC) deployments across accounts.

How do I add users to my project?

{: #project-add-users} {: faq}

To add a user to a project, they must be a member of your account with correct IAM access roles assigned.

To assign access to the {{site.data.keyword.cloud_notm}} Projects service, complete the following steps:

  1. In the {{site.data.keyword.cloud_notm}} console, click Manage > Access (IAM), and then select Users.
  2. Click the user or access group that you want to assign access, then go to Access > Assign access.
  3. For the service, select Project. Then, click Next.
  4. Scope the access to All resources or Specific resources. Then, click Next.
  5. Select any combination of roles or permissions, and click Review.
  6. Click Add to add your policy configuration to your policy summary.
  7. Click Assign.

In addition, users must be assigned the Editor and Manager role on the {{site.data.keyword.bpshort}} service and the Viewer role on the resource group for the project.

How do I estimate project costs?

{: #project-cost} {: faq} {: support}

During the validation process, the starting costs for the project are estimated. You can view the cost details associated with the project from the validation modal after your changes to the configuration are saved and validated.

Who has access to my project?

{: #access-to-project} {: faq} {: support}

Any user that is a member of your account that is assigned access to the {{site.data.keyword.cloud_notm}} Projects service, {{site.data.keyword.bpshort}}, and the resource group for your project can access your project.

I added a deployable architecture to my project, why were multiple configurations created?

{: #da-stack-add} {: faq} {: support}

Some deployable architectures are more complex than others and include multiple architectures that work together. When you add one of those architectures to your project, each architecture it includes is represented as a nested configuration. Ideally, required inputs that you need to configure should be included in the parent configuration, so you shouldn't need to edit each architecture configuration individually.

Can I reuse an existing configuration in a project?

{: #config-reuse} {: faq} {: support}

Some deployable architectures support reusing configurations. These deployable architectures were created by stacking architectures together during the onboarding process. When you add one of those architectures to your project, and you have an existing configuration available in your project, you can choose to use that existing configuration with the new architecture. By doing so, you can reduce costs and reuse the same deployment for multiple architectures.