From Vision to Value: Workfront Planning Release & Roadmap

Transcript

Welcome from vision to value work front planning release and roadmap. So welcome. First thing everyone always asks. And again, if like some folks come in late will pop it back in the chat to but this session is being recorded. You will get the slide the slides are chefs kiss that is thanks to our delightful presenters that we’ll talk about in a second.

But yeah, being recorded any resources we talked about and then the slides will come later today. What are we going to talk about so like Andrea and Lillith and Robin can I believe that everybody talked at the release webinar just a few weeks ago, but they didn’t get quite a lot of time. So this is our opportunity to go through like what was just released how it’s going to benefit you and then maybe just I think there’s a little bit of a sneak peek into what they’re looking at doing. I have to use the cagey we’re like, I don’t want to, we’re not promising anything but this is for 2026.

Okay, so your skill team is here and carry so our plus one skill team member. So all four of us are here, but you’re not here for us. If you need to get a hold of us. We’re at CSS scale Adobe.com but who are you here to see. Okay, so our product team for work front planning. So we have Andrea Lillith and Rob, and they’re going to give us a bunch of different updates, but our first pretty presenter is Rob. Are you ready, sir.

Sure. Thanks. Yeah. Hello everyone. Cool. Let’s jump right into it. So, our first first enhancement so basically just to give a bit of context how this will go, we will present you all our previous enhancements in this quarter, and then we will go to what you can expect in the near future, and then we will do a bit of sneak peek, what you can expect what we’re thinking of in a bit more longer term. So yeah, let’s start from the first one. So this is enhancements for the connected record page. So basically what is the connected record page whenever you have different record types let’s say campaign and tactic, and you make a connection between them. We have given you the ability so that you can create a connected record page for tactics inside campaigns, so that you don’t lose the context you don’t jump into different pages, you are in a campaign you want to see each tactic connected to that campaign, you can just create a connected record page and view all the tactics under that campaign. But this was only available in the full screen mode. So with this enhancement now you can do it also in the model, and previously, the connected record page was just static so the only you cannot make the edits, and we have heard a lot that there is a need. So that if anything is needed to be changed, you can just make inline edits, and you can make it in bulk. So we have added this functionality. So with this enhancement you can now view the connected record page in the model, and you can also do the inline edits, just as you are doing in the main tables.

So yeah, this one is about the connected record page. I think, Cynthia, we can move if there. Yeah, not yet, but I just want to say, I love an inline edit. So just gonna say that. Alright, go for it. It’s also important that when the limits and records and the volume of the things is increasing, we can make sure that our platform will serve your needs, and it will not go down the performance and the loadings with no snow. So that’s why with all the connections we and with all the flexibility, the planning is giving, we understood at some point that we need some guardrails. Because we see that with the connections and with all this graph of things which is happening under the hood. So the system can become easily complex, and we need some mechanisms to cope with that. So that’s why we have introduced this toggle so that whenever you make a connection before this, the back reference field on the other side, so let’s say you make a connection between tactic and campaign, the campaign and tactic connection is also being created on the tactic side. So with this feature, we are introducing the toggle so that you can control whether the back reference is being created or not. And we have added maximum 500 connections per record. So, and our goal here is that whenever you create a connection, we would like to ask you to be like more intentional about whether the back reference is needed or not. Because a lot of times when it’s like categorical data or like it’s taxonomy, the back reference is not so useful. And with back reference is able, the chance of reaching the limit is much less. And if it’s enabled, you can like easily reach maximum number of like 500 connections per record. So this is basically to make sure that our performance we can put under control so that it’s always reliable, usable and scalable. And this number in future potentially can be increased. This is just for now we are setting 500 as a limit, we will see how it goes and make like changes correspondingly. Okay. Yeah, we can move forward with the next one. Okay.

Yeah, so this one is about integration between one phone planning at Adobe Jazz Studio. So basically, Adobe Jazz Studio is for like creating copies and images with AI and activating your marketing assets.

And yeah, managing your socials. Basically, Adobe Jazz Studio has been powered, the PAM has been powered by the work from record types, planning record types. And there were like predefined record types with predefined fields, campaigns, products, personas, activations, channels and regions. What we have added now whenever you have planning and jazz studio together, you are getting out of the box Adobe Jazz Studio workspace with all those record types, and you can control them, you can add new fields into this. Whenever you make any updates inside planning, it’s also reflected on the jazz studio site. And this is because we understood that not every organization is the same, just keeping the same predefined fields and record types is not enough. Every organization has their structure, their workflow. So this is the way we can give like flexibility so that whenever you are planning your campaigns, products, personas, and doing all your taxonomies, you can basically make the corresponding changes and those will be reflected on the jazz studio site, and vice versa.

Cool, let’s move to the next one.

And I will pass it on to Raff for this one. Thanks, Rob. Hi. So yeah, we added for that regarding the views, we added a new views toolbar, right and we added additional capabilities, you can now instantly search in this toolbar, you can also drag and drop the different views to reorder them, and this is per user. You can also see like a clear ownership indicator to see what views are like a private or the ones that have been shared.

I will quickly demo this in a few minutes, and we’ll move to the next one, please.

Also related to the views, we added, we have a more interactive calendar and timeline view. Right now you have the ability to double click directly on the camera to create records. You can also drag and drop the records in the timeline and calendar and you can resize to adjust the timing, right, the duration of the records directly in the views. And the last one is related to the calendar view. And you can also set different height options similar to the setting that you have in the table view. And also there is an option to fit to content to show additional records in the calendar view.

Next one. So some additional enhancements also related to the views. The first one is the ability to use the full screen mode. This is supported in the table, timeline and the calendar view. Also, the second one is about instantly adding options to this select fields, right to single select and multi select. So previously, you had to go to the field, edit the field and add a new option. So now directly when you click on the record itself, you can start typing and you can add the new choice directly from the table. The next one is about the auto population of fields based on applied groupings. So you have a table, you have one group build or different groupings applied to the table. Whenever you create a new record as part of this grouping, the fields that have defined that the grouping will be automatically populated. I will show it in a few seconds. And this functionality and the last one is also an enhancement to the toolbar, right. So before this, if you have like many options in the filter, the grouping, the sorting, it was difficult sometimes to find the right field, right, to filter.

So we added a search in all these toolbar setting options to make it easier to define the view that you want to achieve. So this is important views. I’m going to do a quick demo showing everything that I have described. So I’ll take a… Okay, you go ahead and take it. Thank you.

Okay.

So yeah, the first one, the views toolbar, right, the new view toolbar. So you can see that you can well quickly search for the views. Right now I only have four, but if you have 50, it will be much, much easier to find anything. You can quickly reorder, you can drag and drop to reorder the views and define which ones are the ones that are more relevant. You have the menu here to rename, share, duplicate, or delete the views. And also you can export.

And then you have also the option to create new views from here. So this is regarding the new experience for the view toolbar. For the filter, the grouping, so as I said, we have now a new search. So imagine that you start typing a campaign, for example. So the list is restricted to the search. And also the same, for example, for the sorting.

Yeah, you can search quickly.

And the results are created by the search.

And what else we have for the views? So we said that we have a full screen mode, right? So you can click here on the full screen mode. You can continue working on this table, right? You don’t need to, yeah, you can, you don’t need to exit the full screen mode to continue working on the view. You can see.

And for, we said for the groupings, for example, when you have groupings applied, if you create a new record, like for example, if you want to create one record as part of this campaign time B2B marketing, you can see that the B2B marketing field has been automatically populated because I’m creating the record as part of the new group. So this really helps when you have like, yeah, to create multiple records and maybe you could have different groupings applied. So the information is directly grouped here and populated here.

What else for the fiscal year? Right? We said for the multi-select, as in the select, before the improvement, you had to go to the click to the field, edit the field and then add a new choice, right? So we have these three options right now. So mind that we are planning for next year, so you can quickly start typing 2026. And as there is no result, you can add the choice directly here. So the new option is directly created from there, from the table.

So this is about the table view. Let me go to the timeline to show all these capabilities related to the interactive calendar. So first one is drag and drop. So you can see how easy and quickly you can drag and drop. You can also resize the records easily. And if you double click, you can add a new campaign directly from the timeline. And the same experience is for the calendar view. And the last thing I want to show is for the calendar view. So we have this row height setting here in the menu. You can define here what are the number of records that you want to show in the calendar. And before that, we were only showing two records, right? And then you have to click on show more. But now you have the option to define some standards, right? We sort the standard medium and also the option to feed to content. That was highly requested as well. There is a limit of 500 records when you don’t have a thumbnail to show that when you hit the limit, that’s when you will see so more. But you have until 500 to get to feed to content in the calendar view. So I think that’s it. So I will pass it over to Niamh now. Thank you, Andrea. And hey, everyone. Yeah. Let me quickly share my screen and continue with the slides. So, yeah, I’m going to talk about a new concept, which is called global record types. We have been discussing this a couple of like in a couple of other sessions as well. And yet to get together, we will also review this today and also have a quick demo of the functionality. So if we talk about global record types, so this new concept enables the teams to standardize key record types, key information, make sure that different teams are using the same metadata. And it is very easy to do cross team reporting. So the main gains here are standardization and governance, because the ops admin defines the record type as global and manages it as well from a central like from a main workspace. And then different teams are able to pull it into their workspace at their records there, which will then automatically represent it on the main workspace and will provide easy cross team visibility for leadership. And at the same time, the different teams will remain autonomous. They can continue managing their own specific needs and workflows without having any bottlenecks.

And I just want to highlight that this capability is only available for customers who are on planning plus or if like for the new package types who are on planning prime or ultimate packages. So this is currently in preview and you should be able to see and play with the functionality if you are on one of these upper packages.

So just a quick like overview before demo. So currently what we see as an implementation model for our customers is like there are two types. If there is a single workspace where all the teams are added to one workspace, everyone works together and like they are using the same record types to manage their work, which creates a good like standardization mechanism because everyone is using the same thing. Right. And everyone has the same visibility to cross team information. However, this also creates this extensive need for governance because now the admin team needs to make sure that every change is working for all teams use cases. Right. And there is also a risk of unauthorized data access that teams like may see stuff they are not supposed to see. And also the workspace can get really cluttered because some of the record types are relevant for some teams, but not others. So this is the one approach. The other one is when every team has their own workspaces. So let’s say events will be a separate workspace, social, peer media and etc. And this is good for the teams to be autonomous, to be able to manage their own information. And however, there is no bottleneck for them. Right. Like they are free to make any change that they want. However, the bad part here is that there is no standardization across the record types. So let’s say if everyone is working with campaigns or doing like activities, deliverables or whatever, everyone needs to create their own version of the record type. And this creates difficulty to kind of come up with cross team reports. How do I make sure I can see all of the campaigns that are happening across all of the teams? So the teams don’t have a good way to collaborate together and see what information is kind of being worked on. And also, there is a need for some extensive automation and manual data stitching in order to get this cross team visibility.

So now, like to intend to improve this, we are going to introduce a new model, an enterprise level implementation model. And here we are saying that like there can be one enterprise workspace. And this is where the main global ops admin will define all of the key record types that is essential for all of the teams or the record types that need to be reused across teams. Right. So the ops admin defines this record type, defines all of the main fields that go into it and that are common for every team.

Now, what happens is that alongside with this main enterprise workspace, each team can have their own workspace as well. They can operate in their workspaces. But now instead of recreating their own version of a campaign record type, which would be totally disconnected thing. Now they can pull this campaign record type that was defined on the enterprise workspace and use it locally for their needs. So that like once the record type is added, the teams can go in and add their own records, which will then automatically be rolled up and visible in the main marketing workspace.

So after all of this flow, someone who is part of the enterprise marketing workspace, even if they’re not part of each individual team workspace, they will gain visibility into all of these records. They would actually gain view access to the data. So this is the whole like the main flow. And this way. Oops, sorry. Can you see my screen? Just a black screen right now.

I have no idea what’s happening with my computer. So let me try it again. I think something with the slides.

Sometimes it just slips away. I’m going to tell you that it does that to me. Sorry about this. So I just right click on Chrome if you’re on Chrome. And then yeah, yeah, I think we’re good. It’s kind of.

So anyways, like these are the slides. And now let’s just go and see how this works in reality, right? So here I’m logged in as a system admin. So I have access to the main marketing workspace. And also I have to like events and PR workspaces in the system. In this marketing workspace, I have only John, like he has view access to this workspace, and he does not have access to the other like team workspaces. So at this point, I have defined the campaign’s record type. And I want all of my teams to use this record type on their site. What I can do is I can go to the edit screen.

Advanced settings and enable the like cross workspace records type capability. Yeah. So here I can also decide when I enable this, I think it means that I can add this record type to any other workspace that I manage. And here I can also say, and also is able to add this record type to her workspaces. Because let’s say I know that she’s managing the events team and she may want to pull it into their team workspaces. So when I save this, this point, we can notice that there is a workspace column that is automatically added. So this is a system generated field. It’s always showing which workspace each record is created from. And it’s not editable. And also, if we go back to our workspace, you can see that there is this globe icon and hovering over it, it like this demonstrates that this record type is global and can be added to other workspaces.

So now let’s go to this other screen. And here I’m logged in as Anne, who is the workspace manager for events. And let me actually refresh the screen here.

Okay, so let’s say Anne needs to also start using campaigns for events. And when I now try to add to create a new record type, I have a third option that says add existing. And here, when I select this option, I will see a list of all record types that have been enabled for me from other workspaces to reuse. So I just select the campaigns that was enabled from the enterprise workspace is just added to my workspace as any other record type. And it’s just like that it’s ready for me to use. So if you remember, Anne was not a member of the marketing workspace. So now when I navigate to this workspace, I will just see a blank record type. And what I can do is I can start adding new items.

Right. So let’s first add some dates here, let’s say I want to do some like some So these items, if I go and look at the workspace, you can see that now this is showing the events workspace, right, because these items were added from the event workspace.

And the important part here is that from this workspace, from the event workspace, I’m not able to change or delete the fields that were that were defined as part of the campaign record type by the global admin, right. So all of the information, all of the fields and metadata that are defined on the global level are not manageable or deleteable from here. So we can make sure that it is always consistent and only the global admin has the power to adjust the structure of these record types.

So if I go back to the enterprise workspace now, let’s go into the campaigns.

And you can see that now the event like this event campaigns are now represented here as well. So all of the like items from the team workspaces are automatically rolled up. So this is a system admin user. So anyways, I would get access to it. So now let’s go to this other section. And this is where like I’m logged in as John, who was only part of the enterprise workspace with the view access. So he doesn’t have access to events. He only has a view access to enterprise marketing workspace. And even if John logs into the system, he can still see the events records and records here as well. Just I’m showing this to highlight that anyone who is part of the global workspace, regardless of their access to the other workspaces, they will get automatic access to cross team information.

And this is also like allowing us to, let’s say, create some timeline views. You can group the information by workspaces. So this way you can understand what team is working on what. As you know, we also like have the option to resize our information here. So basically like this, this is a really good way to see what each team is on and where they are at with their work.

So this is the current state like these are the main benefits at this point. So coming back to the slides, just go to.

Anyways, I will just let’s now talk about what’s coming next, not only with global record types, but with overall our system, right? So with global record types, the next big enhancement that we are currently working on is to allow the team workspaces to extend the global record type and add their own field. So, for example, and in the events workspace would go in and create an unlike event description or speakers or some other field that is only relevant for events. It would not be represented on the other workspaces or for the global workspace itself. We are building also the ability to define the global record type permissions in each workspace. So, for example, if I add the campaign’s record type in events, I can make it view only for all the contributors. And I can only add a couple of people who are able to actually contribute to the record type. We are improving the overall experience. We are now also showing which workspaces the record type is added on. We are going to support team specific intake and automation. So a lot of enhancements that will be coming to kind of enhancing the experience of using this record type in team spaces so that the team workspace managers are not dependent on the global ops admin for any change that they need. Right. So, yeah, a lot of enhancements coming to this concept.

Other than the global record type, we are also working on introducing more enhanced access controls. As you know, right now we only allow workspace and record type access controls and record type is, to be fair, quite limited. So you can only make it view only and add certain users there. And it’s not possible to restrict it at all. So we are currently working on record permissions, which will allow you to define who can have how much access to each record or even restrict the whole record from certain people. Let’s say it contains some sensitive information. And after the record permissions, we’re also going to extend the same permission controls to columns. So you could even say like this column, only these people are able to edit information in this column or these people are not even able to see information in this column. So a lot of enhancements and very granular levels that will be introduced and our plan is to work on this in Q1 of 2026.

So the other enhancement I will just talk very quickly that will be coming soon is the ability to reassign owners for workspaces. So as you know, currently, if you create a workspace, you’re set as the workspace owner, and that’s not editable, like it’s not possible to change it. So even if, like, let’s say someone changes roles, or if you need to reassign the management of a workspace, you will now be able to set another user as the owner of the workspace. But you will still be able to have multiple workspace managers alongside, right? So this is just like defining one main owner person for each workspace.

Okay, I think these are all from my side. And yeah, I will let Rob continue with some upcoming enhancements.

Cool. Thanks, Lily. Will you go to the next slide, Lily? Next one? Oh, sorry. You already did it. So yeah, okay.

So about the hierarchy set breadcrumbs and just a bit of background. So when we introduced planning and difference between like current workflow system and planning in work, what we have the predefined set of the objects right portfolios, programs, project tasks, subtasks issues, and they are hierarchical. And on the planning side, we have, can you go back, I think we move to the automation again. Yeah, cool. Thank you. And on the planning side, we gave a lot of flexibility, you can create different record types, you can make connections between them, you can like select the type of the connection, whether it’s many to many, one to many, many to one, one to one. But what we understood is that all of these connections are the same, and there is no any hierarchy between them. But we don’t want to expose and enforce any hierarchy. We heard from a lot of our customers that they have specific like sides of like workflow and their objects and their hierarchies. With this enhancement, we are going to introduce a custom hierarchy. So basically, you are going to be able to create your own hierarchy inside the workspace. And different workspaces can have like different hierarchies. Let’s say there is an event team and the social team event team can has like different record types, and they can define their own hierarchy, and the social team can do like just corresponding to their workflows. And inside the workspaces, you can have not just one hierarchy, but you can have also multiple hierarchies. Just as the picture shows, you can set like all initiatives, campaigns, tactics and projects as one hierarchy. And in the same workspace, you can have like goals and experiences as a child to that hierarchy. So this is how it’s going to work and what is what is going like hierarchies are going to power also the breadcrumb system. So currently on the workflow side, we have the breadcrumb system, but on the planning side, we don’t have any breadcrumb system. And this makes a system a bit confusing. From the navigation perspective, especially because you don’t understand like the hierarchy and how to quickly move between the records between the objects. And this breadcrumb system is going to work in planning, but it’s also going to work across planning and work from. So regardless where you will be in the system on a record or an object, you will see the breadcrumb system and you can quickly navigate, click and navigate to that specific object. And also in the future, and this is a bit future thing, we are thinking that the hierarchy system is going to also power the permission inheritance. So basically, now in work front, we have your portfolio and when you have a program and you have specific like access levels on a portfolio, it’s being inherited on a program and afterwards, of course, you can refine it. And we are thinking that the hierarchy system we are going to introduce is afterwards going to be used also for permission inheritances.

So this is it about the hierarchies and breadcrumbs. Let’s move to the next one.

So regarding the automations, so we have the automation system currently in planning. It’s a basic automation where you can set up a trigger button click and you can set up the action and the button is appearing on the UI. You can whenever you are ready, you can just click the button and the automation will perform the action. But we think the true power of the automation is the rule based automation where there is no like human intervention. You are not clicking any buttons, but you are just setting up the rules, the conditions, which is the trigger part. And whenever the trigger and the condition is met, the automation will perform the system itself will perform the actions. So in this case, it’s going to be not just like one condition, we are going to introduce like multiple conditions with and or logics. So basically you can define the rules. Let’s say you want the status whenever the campaign status is ready, you want the projects to be created and the system will create will create the objects. And of course there are some enhancements afterwards, we will introduce the execution history log so that you can see what the system performed, what are the failures, what are the successes and what are the actions performed by the automations.

So yeah, this is something which is probably coming in a month. So this is the next like feature set we are going to introduce for the automations with some more enhancements. So yeah, let’s move to the next one. AI guided workspaces set up. So this one is interesting and this is a bit innovative work we are trying to do. And in Adobe, we want to invest a bit more in like AI and you can expect a lot of AI features and functionalities coming in the future. So this is one of the first steps. So creating workspaces and understanding all the record types, fields, field types, connections, views, intake bonds is a bit tough when you are creating one, and especially when you are new to planning. So with AI guided workspace set up, we are introducing just the conversational assistant where you can like just describe your like working way, what is your marketing organization, and the AI will just like ask you some questions to get more details and understand better the context. You can also upload different documents or images with the workflows and AI will extract all this information. So basically it’s trying to get the information needed and it is going to be smart enough to also guide you about the best practices, how to create the workspaces. And just with the conversation, you can create a workspace. It is going to create a preview. So you will just see like what’s happening. If there are any refinements or adjustments needed, you can just refine all of the settings with the conversation. Let’s say there is a field of regions and you want to make it from single select to multi select. You are just typing it and real time it’s changing the preview. Whenever you see like everything looks good and you are ready to move forward, you are just clicking the generate workspace and the workspace is created with all the record type sections, fields, views, intake forms, and probably with automations also.

So yeah, let’s move to the next one. Enhanced connection views. So we speak about the connected record pages that they are going to be in line editing in this connected record pages and it’s going to work on the model. But currently it’s just limited to one view. So there is no the view system in this, so you cannot create new views. You cannot share the views. Basically, we are going to introduce the new system. The same dropdown that Andrea is showing about the views and the view sharing. So you can also access from the connected record pages and it’s going to be universal. Regardless of whether you are creating a view from the main table or from the connected record page, it will be added to your view library and you can access it from the main table and also from the connected record pages.

So yeah, this is a bit of small enhancement to the connected record pages. Little John, let’s move to the next one. Customer care. So this is something we call, which is not a big thing, but we see a lot of pain points and small fixes that we can make and we are constantly investing in this.

So we are going to add user friendly names to our field options in API. So we have heard a lot that IDs, especially when you create the fusions scenarios, they are not useful. It’s really difficult to find them. So this is the way for us to give you the ability to just quickly create and find names and create your scenarios or use other like API tools you are using. The next one, supporting people builds and lookups. Currently, when you create a connection, you cannot bring people build as a lookup and especially this was painful for projects. Because people were connecting projects to their records and they were not able to bring the people field as a lookup.

This is the same for other reference fields, but this is the first step we are making towards solving this problem. So you will be able to bring people fields as a lookup for your connections. And the last one displaying intake form name on submitted records. So we understood that there is a need to track because when there is an intake form and there are requests, they are after being converted to records. A lot of people want the reference like from what intake form it was created. And this is for reporting purposes mainly. That’s why we are going to add the intake form name as a field probably. We are still thinking about the solution, but basically you are going to be able to see all your records from where they are originated from what intake forms and you are going to be able to do the reporting on this.

This is it about the customer care and small enhancements. John, let’s move to the next one. And this is about our next initiatives, which we are thinking around. We are currently actively exploring and doing some work here. So I will just give the high level overview of the focus areas. So, yeah, as I mentioned, we are investing a lot in AI and it’s not only for the workspace creation, but we are also thinking about like pre-creation, about like system designer overall and across work from there are also like project manager agent. These are basically the things that the agents that could help you to perform the actions which are repetitive, which are taking most of your time. So we are trying to explore and understand what the AI functionalities for the next year are going to be for the work from the system overall. For the briefs, so we currently have the detail pages, but we have heard a lot that the briefs in marketing world needs to be like more narrative style with rich media, with the ability to be customizable, flexible. And we understand that our detail pages currently are just like metadata. So we are thinking about like enhancing our detail pages or introducing the new page type, which will be called briefs. Basically for you to be able to create different type of briefs for your stakeholders and for storytelling and just like aligning with the stakeholders. The next one is document attachments. So currently in planning, we don’t have the document attachments and we know that document attachment is a big thing. We know that a lot of our customers are expecting and this is like a table stake. So this is something we are going to work on. This is just a bit of like complex technology and we don’t want to do a disconnected system again. So that’s why we are thinking about like universal and centralized storage across work front and maybe other AP products. So that’s why this is taking a bit more time, but we are working on this.

For the next one, cascading fields, we also call this dependent fields. This is when you have two fields, let’s say like products and activities. And based on the products and activities, whenever you select a product, you want not to see the whole list of the activities, but you want to see just the narrow down list of activities corresponding to that product. Or you have a region and the country. Whenever you select a region, you want the selection of the countries to be narrowed down just to correspond to that region selected. So this is about the cascading fields.

Further permission enhancements. So as Lelit mentioned, we are working heavily on the permission system and we are going to introduce the record level permission, but after it, we are also going to introduce field level permission. So basically you are going to have workspace level, record type level, record level and field level permission. And we believe that with this system, it will give the ability of different permutations and will cover most of the needs about the governance.

For archival and restoring. So there are two things here. One is again going to more of like system scalability, reliability and performance. So that as you work on planning, as you work inside planning, the records are going to be added a lot of like data and the volume is going to be increased. So we are going to give you the archival functionality partly to solve this problem. But also we understand that archival is also solving the relevance problem because you don’t want every record to be there all the time. You want the relevance records, maybe like the campaigns for the last year or like three years before you don’t want them to appear there. So we are going to think around the archival mechanisms and archival functionality and also restoring. And for the audit logs, this is again all this time to the governance.

So on a work front side, we have audit logs, but on a planning side, you do the actions. We have a couple of things on the record detail pages where you can see the changes made to the records. But we want a more robust like audit log system so that whenever something happens, you have full control and visibility what has happened. And just traceability, visibility to what is happening inside the system by different users.

So, yes, this is basically it about the future roadmap and next initiatives. I will pass it back to Cynthia.

Yeah, like just for a second, I like how like Rob, you just sort of like in the middle of your presentation talked about the hierarchies and the campaigns. Those of us that have been work front hours for a very long time, like that is literally the ability to define, OK, this is where we want it. Like that’s a big deal. Like some of you all that may not like that’s a big deal. So I’m just going to say thank you to thumbs up for that. That’s amazing. I know we have some questions, but I do want to address one thing that Greta put in there. And Carrie, thank you for answering that question. But I want to address it to everybody. So like y’all know that I’m financial services background, not marketing.

So I can think of a bunch of different ways that this would have solved a lot of challenges in terms of I had an international operations at its own business unit. I had I.T. in its own business unit. H.R. right. Like marketing was in there, but it was a bunch of other departments as well. So just anybody that’s sitting here going, well, these are marketing examples. Take it off. Like you don’t have to like you can just take that word out and just think about like how do you set up your initiatives and think about like. Planning as a phase that moves into workflow and those outside of marketing, like we know like an I.T. project has a very long runway of planning. And so you could totally use that. So I just want to throw that out there before we start into the questions.

The first questions that I want to address really quickly is for the global record and this may be for you, but all three of you all. So I know Ross has a question and I believe Lauren asked a question about the global record types. And it feels like their questions. The answer is yes. But I’m just going to like throw Ross’s out there, like for agencies, could we set up planner for each client having their own workspace, but leveraging that enterprise level record type to ensure consistency. But then the way that you showed it, they could also not see anything that they’re not supposed to see. Seems like that’s a yes. Yep. That’s exactly what the global record type is intended for. So keep teams separate, keep them focused on their own work and at the same time, make sure that they are using the same structure, the same metadata. Right. And then you have this cross agency visibility into what’s happening there.

Awesome. And then from Lauren, just like what’s the best practice in terms of like sharing workspaces? Like, I mean, obviously I personally would also prefer team level versus individuals. But what is your thought on that? So like workflow objects, for example, in projects, you know, we have a limit of you can add 100 sharing groups. Right. Like you can add 100 individuals, 100 groups, or 100 teams, for example. Right. So the best practice here is to try and add as many like, let’s say, not individuals, but groups, teams. And it all depends on like how you define your workspace. Right. So very often we see the group sharing that is kind of most used to for this, like for this kind of bulk sharing. Yeah. So I would definitely recommend you look into that rather than doing individual use of sharing. Yeah, I agree, too. Okay. So I’m going to I do want to say a lot of people are like, Rob, when do we get document attachments? You all remember on the slide it said future. Like I will say this, like, please keep coming to these events. Like this is your product team when they are presenting. They’re also sort of getting in the Q&A and in the chat, like what are the priorities of customers that have planning or they want to get it? So like that’s a fair question, but also future magical future that we’re looking for. Okay. So I’m going to if we’re cool. I know there’s some questions and you all have been answering in the Q&A pod, but I’m going to go ahead and we do have a few minutes to just turn everybody’s mics on if that’s cool.

Let me do that real fast.

All right. One second. Teams, you’re going to be my friend.

Allow mic for attendees allow camera for attendees. Okay.

Anybody got a question they want to ask? Live? I did see Rob come off mute when you asked about the general timing for documents, maybe he will. Oh, are you going to give us a date? We won’t hold you to it.

You’re not. And now Rob just leaves the session altogether.

I have a question.

Yeah.

So go ahead. Yeah. Yeah. How how this is the I mean, do we have any module for work front fusion for work front planning? Oh, that’s a good question. Yes. Someone. Yeah. Was that did you ask that in the chat? I’m so sorry. That’s a great question. Yes. Yes, we have. We’re inside fusion, if I understand it correctly. So you are asking whether there’s planning module inside work inside future. Right. Yes. Yeah, there is. There is. And it has like most of the actions which are available via API. And we are going to also enhance our API with the version two API, which will include like more things, more actions. But yeah, the basic one is already inside fusion.

And do you have any like we have API Explorer, right? Are these modules available in API Explorer or from the API Explorer or do you have a separate documentation for work from planning? With respect to API Explorer? Yeah. So I’m not sure for that one. Let us follow up on this to see. Leila, are you aware? We have a documentation for work front planning API. So like it’s published and you should be able to go to the Adobe developer’s side, if I’m not mistaken, and find it there. So if you go to experience link and search Adobe planning.

Yeah. API, you should be able to find those and the article contains all of the links to to the explorer.

I’ll try to find it. Leila, if you have your hands on that link, would you mind sending it? But yeah, that’s a really good question. If you want to share, I can.

Yeah.

Oh, you’re sure. Rescue.

Thanks. Oh, thank you. Appreciate it. Oh, this one is separate from the looks like it’s a separate one. OK, so that is a great question. I’m so glad you asked that question. So when we share the API explorers from now on, we’ll do both planning and sort of the one that we always use for reporting.

I think we have another question.

Abhinav.

Yeah.

Hi, team. Thanks for the wonderful session. I just have one quick question. I saw that as part of the road map, like there would be like for the features that will enable like more more automation features related to project conversion, etc. Right there in planning. So a lot of a lot of users might already be using fusion for activities like project conversion or issue creation, etc. So I just wanted to understand like what happens to like also like existing automations which exist in fusion. Like will this be like automatically detected by system or like like what should be the approach taken in case like if the team wants to shift the automations to planning from fusion. Yeah, that’s a that’s a really great question. So basically the difference between like automations we have in so headless, which we call headless automations and infusion. This is in-app automations and it’s going to be like basic simple automations at this point. And infusion, you can create like multilevel with complex logic and routing logic, automations with third party tools. So regarding whether the system is going to detect, probably not. It will be if there is like simple automation which you have set up both inside fusion and also you have created with the headless inside planning.

It’s going to be like you to go and reconcile this, understand which one and maybe fusion scenario could be deprecated in this case or deactivated. But yeah, as a system, we are not detecting whether there is automation, which is just exactly the same inside headless and inside fusion. But that’s a good one. That’s that’s a good question. And I think we will think around it. But probably there are two different systems. And that’s why there is no like one to one connection between automations inside fusion and headless.

Awesome. Got it. Yeah. Thanks. Thanks, Robert. Thank you. Dominique. I’m going to do what’s real quick and then you’re next. But I just want to post this out here. So the questions that we get all the time are how do we get started with planning or how are other people doing like planning? So Syracuse, I know we had the one customer, which is great. Like if you have not seen Southern New Hampshire University, you should totally go watch that. This is Syracuse University and they are going to talk about how they are just like sort of getting started. And they’re already seeing connections across their organization and they’re using planning like in a completely like they’re using this in a completely different way to support all their processes, including workflow. So that is December the 9th. Please don’t miss it. You’ll get the link in the follow up. You’ll get all of these planning resources, including that event I just talked about is on this page. We have so many events coming up through the end of the year, including like a fusion event, automating naming conventions for like we have a bunch of stuff throughout the end of the year. And then please, if you do get a chance, we do have a little bit of a longer survey, not the one that we just posted. But this is a brand survey because Nicole, Leslie and I are going to literally start our 2026 planning in Chicago this week. So please let us know what you think. And OK, I’m going to stop and Dominique your question.

You guys. Yes. Little so as we echo problems there. Three quick questions. The first two quick ones about the API. You all mentioned version two is coming. What’s the I know it’s probably going to be next year. And when is that? Are you thinking what quarter and what impact is that going to have for folks like me who are leveraging work from planning and also work from planning internal API? Yes. So this point we are looking at Q1 26 for the next version of our API. And that’s going to have more capabilities for creating, updating or getting the workspaces record types fields. So right now, our actions in public API are limited to records. Right. So now we’re also going to extend it to additional like, yeah, deep data in planning as well.

Yeah. So what was the second question? I think I what does that mean for someone like me who’s or like us who we’ve heavily invested in fusion planning? Are we looking at a change for all the existing modules or will the transition be pretty much be seamless and we won’t need to go back and roll? Yeah, it’s not going to affect the existing API. So we’re just enriching and adding more endpoints to it. Right. So you don’t need to do anything. Nothing will be broken. It’s just kind of supporting more more functionality there. Right. And my last question was from earlier. If I recall, not all the work front users get access to planning, you know, based on license and things like that. With the hierarchy changes that are coming, I heard something that about defining the hierarchy in planning and then kind of transitioning down into work front. If users don’t have access to planning, who have access to just work front, how does that affect them, if any? So actually, the way that planning licensing works today is that you get like you don’t get to choose that this user only has access to planning. If the user is on work front, they can have planning and workflow. Right. Like it’s not disintegrated from each other. So the way here is that like if you have access to let’s say you have a project and it is linked to some record in planning. If you have access to view that record, you will be able to see that information on the project side. So we don’t have that kind of limitation.

So the new hierarchy system doesn’t affect your user license at all. I’m only referring to the navigation breadcrumb section.

Not licenses, but to access of data. Right. So let’s say if this project is linked to a campaign and you have access to the campaign, you get to view the project as well. So it’s very similar to how the portfolio to program to project inheritance works. Okay. So it sounds like there’s still a certain level of thought that we would need to put into consideration as customers. If we’re doing this pre-work in planning for how we’re organizing our hierarchies and things like that anyway. Thank you. Yes. Yeah. So just to pop in a quick history lesson, Dominique, I think that that is exactly I know there was a lot of discussion a year plus ago when when work front planning rolled out, can we just buy a few licenses for planning? And it was, oh, actually, no, like you either own planning or you don’t. And it was because of this vision. Right. It was because if you have access to workflow or work front and you’re actively working in that, we want to have everyone be able to view with the appropriate permissions back into the planning module. So just want to give that. Yeah.

So we’re two minutes over and I want to be respectful for our product folks. So anybody that’s got continued, I will tag Andrea Lillit and Rob and the experience post. We can continue those conversations out there. I just want to say a couple of things. Like if you are interested in planning and somebody asked about test drives, whatever those kind of questions, please kind of focus those towards your sales account manager because they will they can help you with that. And just as a side note, this team, this team that is on this call, we’re going to do a lot more for twenty twenty six. And I’m going to like present those like ideas like how to implement across because that was what I did as a job. So we’ll figure out some best practices in terms of that in twenty twenty six. Lillit, Rob, Andrea, I know it’s late, especially especially in Army. So thank you very much. So late. Thank you. I’m so late. So thank you. You all are the best. And we’ll see you next time. Right.

We didn’t scare you off.

Thanks everyone. Thank you. Thanks everybody. The great discussion. Bye bye.