This article aims to explore the requirements and challenges that Intent-Based Management(IBM) systems should look towards to deliver proper automation management in multi-stakeholder 6Gscenarios. To do so, the evolution of the telecommunications actors is presented to identify how they willinteract with the use of intents and what IBM systems must face to fulfil with the tenants expectationswhile interacting among other IBM domains (aggregation vs. federation models). In a second step, thisarticle presents how the IBM systems functionalities should be organized (based on standards research andcomparative) and a set of enablers using them to properly deliver the automation needed to accomplishthe requests done by the tenants. On a third step, a set of End-to-End (E2E) intent-based services aredescribed to illustrate how the different enablers (and the functionalities they use) may work to reach theE2E service goal. Finally, a set of experimental results related to how intent conflicts should be manageis presented, followed by the conclusions.