Posso criar uma organização para um cliente, ao invés de criar só um projeto?

[Fabricio Valle]

Estou estudando pemissões e li sobre permissões para clientes no Jira Service. Minha questão é a seguinte: minha organização vai prestar serviço voluntário para um associação sem fins lucrativos (ONG). Inicialmente farei um site, e estou estudando as permissões porque não quero que o usuário deste grupo veja tudo na minha organização, mas apenas o projeto de construção do site.

Acontece que nossas relações é de longo prazo e muitas outros projetos deverão ser realizados, e não apenas construção de sites. Então me veio à cabeça a ideia de criar uma outra organização,, voltada para este grupo, que deverá evoluir muito.

É possível que essa nova organização na minha conta deverá parmanecer isolada de outras organizações? É recomendável que eu criar essa organização ao invés de apenas o projeto do site, prevendo a expansão da nossa colaboração?

Poderia continuar estudando, mas preciso tomar uma decisão rápida, pois estamos atrasados no projeto do site. 

Nota: meu objetivo é incentivar o grupo a adotar os produtos da Atlassian, para que a organização possa acelesar seu crescimento

Detalhe: meu plano por enquanto é free.

@Diogo Teles 

[Fabricio Valle]

@Trudy Claspill , I liked your tip, but I have doubts:

1- as I will be the one leading the projects, I will have to include myself as a user on this new site. And I'll have to add a user to this new site to begin with. How is the calculation of users in an upgrade to the standard plan?

Will it be two users (me and the NGO leader), or three? That is, will I be calculated twice?

2- the new organization will be 100% linked to mine and future payments will be made by a single credit card or we can, for example, in case I opt for the upgrade, add two credit cards, one for my organization and the other for the organization of Togo?

3- Do you think it is important for my future certification that I have experience with the paid version? In other words: are there many more features in the paid version than in the free version?

[Trudy Claspill]

1. Each product on each site has its own licensed user count that is used to determine billing. For each product each user with Product Access will be counted. 

If you already have one site that has Jira and you are a licensed user of it, you count as one user for the billing of that product.

If you set up a second site that has Jira and you are a licensed user of that Jira instance, you count as one user for the billing of that second product.

You are counted once in each product to which you have access. Each product can be on the Free plan if it has no more than 10 users with Product access.

2. Let us be clear about what you mean when you say "organization". Atlassian Cloud has the concept of an Atlassian Organization. When you first signed up for the Free Jira product, that product was installed on a new site, and that site was created under a new Atlassian Organization for which you are an Organization Admin.

If you set up another Site under your existing Atlassian Organization, and in that new site subscribe to products that will be used by the NGO, those sites and products are part of your Atlassian Organization. The Organization Administrators for you Atlassian Organization will automatically be Site Administrators for all Sites and all products under your Atlassian Organization.

If you upgrade one of the products in one of the Sites to a Standard Plan, you will need to enter credit card information. The credit card information is entered per Site and will be used for billing of all products under that Site. Each Site can have different credit card information.

3. There are features in the paid plan that are not available in the Free version. These documents talk about features that are available in the paid plans that are not available in the Free plan for Jira. In addition, there are features available in the Premium plan that are not available in the Standard plan.

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/

https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/

Here is a similar document for Confluence.

https://support.atlassian.com/confluence-cloud/docs/learn-about-confluence-cloud-plans/

Certification exams do include questions about the features that are available only in the paid plans. If you have no experience with those features that will likely lead to incorrect answers and reduce your chance of attaining the certification.

[Trudy Claspill]

Olá @Fabricio Valle ,

Se você deseja administrar um conjunto de produtos Atlassian (por exemplo, Jira e Confluence) para esta ONG, permitindo-lhes ter vários projetos Jira e vários espaços Confluence, mantendo-os isolados de outras pessoas que usariam os produtos, então você pode configurar um novo site para eles em sua organização Atlassian existente.

Um administrador da organização pode acessar https://admin.atlassian.com, navegar até Produtos, selecionar o botão Adicionar produto e selecionar Novo site. Isso permitirá que você crie outra instância do Jira com um URL de site exclusivo.

Você pode gerenciar o acesso a esse site/produto para que apenas a ONG e aqueles da sua equipe que administram a Organização possam acessar o site/produtos, e da mesma forma não conceder-lhes acesso ao site/produto que sua empresa já utiliza.

Se você os segregar dessa maneira, não precisará gastar tanto tempo se preocupando com permissões em projetos individuais para manter os projetos da sua empresa privados e invisíveis para os usuários da ONG.

---

Hello,

If you want to administer a set of Atlassian products (for example Jira and Confluence) for this NGO, enabling them to have multiple Jira projects and multiple Confluence spaces while keeping them isolated from others who would use the products, then you could set up a new Site for them under your existing Atlassian Organization.

An Organization Admin can go to https://admin.atlassian.com, navigate to Products, select the Add Product button and then select New Site. That will allow you to create another Jira instance with a unique site URL.

You can manage access to that site/product so that only the NGO and those of your team that administer the Organization are able to access the site/products, and likewise not grant them access to the site/product that you company is already using.

If you segregate them in that way, then you don't need to spend as much time worrying about permissions on individual projects to keep your company's projects private and invisible to the NGO users.

Can I create an organization for a client, instead of just creating a project?

I'm studying permissions and read about permissions for clients in Jira Service. My question is the following: my organization is going to provide voluntary service to a non-profit association (NGO). Initially I will make a website, and I am studying the permissions because I don't want the user in this group to see everything in my organization, but only the website building project.

It turns out that our relationship is long-term and many other projects must be carried out, not just building sites. Then the idea of ​​creating another organization came to mind, aimed at this group, which should evolve a lot.

Is it possible that this new organization in my account should remain isolated from other organizations? Is it recommended that I create this organization rather than just the website design in anticipation of expanding our collaboration?

I could continue studying, but I need to make a quick decision, as we are behind on the website project.

Note: My goal is to encourage the group to adopt Atlassian products so that the organization can accelerate its growth

Detail: my plan for now is free.