Skip to main content
Natalie B
January 27, 2021
Future Consideration

Change tiers in org charts in Lucidchart

Related products:Lucidchart
  • January 27, 2021
  • 54 replies
  • 1897 views

Are you able to manually state what 'tier' members of staff should be. We have instances where different tiers/levels report into the same staff.

For example this picture I need Head of Development to be Tier 3 (not 2) even though the direct report is still into Tier 1. The child links of Head of Development should also be moved down to Tier 4 (not 3).

 

Pinned Reply By Chloe

Thanks to all who have commented here! This is a great request and one we’ve seen consistently, so we will keep this high on our list of future considerations. Thanks again for taking the time to share context with us.

Comments

Ambar D
Lucid community team
April 14, 2025

Hi ​@tim.steinebach, thank you for adding to this thread! Your upvote, feedback, and detailed example are excellent ways to indicate your support for this idea. 

May 15, 2025

Hello ​@Ambar D,

just wanted to let you now that we meanwhile tested your trial version comprehensively and already prepared a database file to use Lucidchart as our organizational chart tool in the future. But our management decided not to order until this must-have feature here is implemented. So we’re waiting now for a solution by your Developers to be provided hopefully very soon. Thank you for keeping us updated.

Best regards

Marc

Ambar D
Lucid community team
May 30, 2025

Hi ​@marcpuenger, thank you for this feedback. I certainly understand why this is an important feature. Detailed comments like yours, along with upvoting this post, are great ways of showing your support for this to be implemented. 

 

August 5, 2025

Hi, is there a timeline as to when this feature will be incorporated ?

Ambar D
Lucid community team
August 6, 2025

Hi ​@Sunmeet A

Unfortunately, we do not have a timeline at this moment. Your feedback is still highly valuable to us. 

The “future consideration” status of this idea means that while the product development team isn’t actively working on this, they’re still interested in hearing about what you’d like to see implemented and they may revisit this in the future. Upvoting this post, and if you’re willing, adding details on your use case and what you’d like to see here are great indicators to our product team that this feature is important to you!

Thank you for taking the time to leave a comment on this thread to show your support for this.

August 13, 2025

Hi ​@Sunmeet A

Unfortunately, we do not have a timeline at this moment. Your feedback is still highly valuable to us. 

The “future consideration” status of this idea means that while the product development team isn’t actively working on this, they’re still interested in hearing about what you’d like to see implemented and they may revisit this in the future. Upvoting this post, and if you’re willing, adding details on your use case and what you’d like to see here are great indicators to our product team that this feature is important to you!

Thank you for taking the time to leave a comment on this thread to show your support for this.

Hello Ambar, we understand that the product team is limited in capacity. They can only work on some ideas, not all.

BUT, this request is now open for more than 4 years. It got over 1000 Views, 45 replies and 43 upvotes. EVEN if this is not the most upvoted post, it has so much attention and is open for so long. This can be really frustrating, as it should be not too hard to implement it. It is really a Key feature. 

Everything is said about this topic. It was explained several times, using picutres, graphics and text. Everyone is talking about the same feature and has the same expectation of how it SHOULD work.

Sadly this thread does not get the attention from the product, which is what i don’t understand. I feel like it does not matter what we do. Because you have all the information you need. There is nothing more we can tell you or the product team about the feature. You got a complete bluebprint of what we want. Now it is your turn to start developing it.

Please, please consider moving this post to a different status than “future consideration”. Otherwise this topic will be frustrating to so many people, and our company is not willing to buy a product, that takes so long for a little key feature to be implemented. And i think others feel the same way.

Thank you, for your time and interest in this topic. I am looking forward for the product team to start working on it.

Micah
Lucid community team
August 13, 2025

@Username_213123 Hi! I’m Micah, another community manager here at Lucid, and I wanted to jump in. 😊

I hear your frustration loud and clear - it’s tough to see a request with so much community support sit in "future consideration" for so long. You've provided a comprehensive blueprint and what you’d hope to see in this experience.

I've shared your feedback directly with the product team, emphasizing the long-standing nature of this request and the strong community demand. While I can't make any promises about a timeline or a change in status, I want to assure you that your message and the community's passion have been heard. We know how important this feature is, and your input is invaluable as we plan for the future.

Thank you for your patience and for continuing to advocate for this feature. We appreciate your dedication and hope to have a more positive update for you soon.

Alex Y
October 13, 2025

Hi ​@Micah, this has recently come up within our organisation and like many others we have employees at various tiers reporting into a manager and wish to flatten the structure to represent our organisation. This really is a critical feature, it is unfortunate as there isn’t even a manual way to adjust this as if you try and say drag down a employee box in the chat it springs back up to it’s automation position so there isn’t even a manual workaround for this! 

Ambar D
Lucid community team
October 14, 2025

Hi ​@Alex Y

We really appreciate your advocacy for this feature and for letting us know just how important this is to you and your organization. I certainly understand the need here, and we have shared this feedback directly with our product team!

Your comment and upvote are excellent ways to indicate your strong support and need for this, and I hope to share good news on this front soon.

November 21, 2025

Is there any way to exclude this placeholder/phantom box from the total employee count in the org chart?

I need to maintain accurate headcount statistics while using this visual workaround. The blank box helps achieve the correct visual structure, but it's being counted as an actual employee in the total count.