Hi Gwen,

Allan made a nice post about this that you could read.

http://labs.episerver.com/en/Blogs/Allan/Dates/2009/1/Neat-Trick-Modifying-Edit-Mode-Tabs/

In short the attribute your looking for is:

    [GuiPlugIn(Area = PlugInArea.EditPanel)]

An edit panel plugin puts a tab alongside View, Edit, Version List etc. The Content, Scheduling,... tabs are below the Edit tab and are simply visible or not depending on whether the page type has a property defined to use that tab. When you edit page type properties in admin mode you can select the tab they end up on. There's also a funciton in admin mode to edit the tabs and add new ones.

If you want to put something on a tab there which isn't a property I'm not sure it's a good idea. It might confuse the editors and probably interfers with the general work flow in EPiServer (page leave check, populating properties...). But there isn't really anything stopping you from developing a custom property type which doesn't read or save any data, but only acts as an agent to get your control into your tab by letting it be part of the custom property's edit control. Then just add that property to the page types where you want the tab and control visible.

That can be done, but I tend to agree with Magnus here.

But you could either make a control adaptor, or add a property that is in new tab, and add your user contron in the CreateEditControls()