You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
from this article here and a few others, I learned that hiding or deleting the "Share with <organization>" field from the form used on a Customer Portal is not possible at all.
Nevertheless, I noticed that the two projects I created last, do NOT show that field, exactly how I want it! When I create new projects, using any of those projects to inherit the configurations (so with "Share settings with an existing project" checked), the new one also doesn’t show the "Share with <organization>" field.
This is project "Accounting" where the mentioned field is NOT showing up:
This is project "Pillar" where the "Share with <organization>" field is shown. I can't find a way to hide it.
These are the "Accounting" project configurations:
These are the "Pillar" project configurations:
They look the same.
Can someone help me to understand, why that difference and how to change it in the project that IS showing the "Share with <organization>" field so that it is not shown anymore?
Can you validate if the Organization is created for this project as well?
To do this, do the following:
On the project home page, click on "Customers";
Check if there is any "Organization" registered.
If there is, check if your user is registered within it.
If there is no organization, then you will need to add it to the project.
If it's still not enough, get back to us so we can continue evaluating.
Hi @Fernando Eugênio da Silva and thanks for your reply!
Your hint took me to confirm that only in the "Pillar" one, does have an organization in it.
If I remove the Organization, but the few users within it are added as Customers to the project, I guess that won't affect them at all, right?
The only impact, I believe, is that users who previously had these tickets shared by the organization will no longer have visibility over them, only the user reporter.
In addition, there are no impacts that can occur if you do as you said.
Organizations for JSM projects are the same as boards for JSW projects = Individuals by configuration.
If the organization reappears in your project, you should review whether someone has not replicated their creation in the new project.
It would also be interesting to evaluate the permissions of the JSM settings on whether only admins can create and manage organizations or if agents can do it as well.
This is a good case to investigate.
Good job! :)