To make it display globally, you'll need to put it in default.aspx.

You could put your HTML directly in that file so that it displays above everything else.

This sounds like an interesting challenge though, I bet I could come up with some server-side code that you could add directly to your skin so that it would inject a module from your host portal into that area.

Let me give it a little more thought, but it shouldn't be too hard.

Both would eventually get what I want.  Imagine if you will...

I am taking care of a client that wants an Intranet but wants to have the business divisions seperated into different portals.  Now as the IT manager I will set up portals for each of the divisions and give someone admin rights for each of the different portals.

The kicker....

HR tells me that they want to have some announcements posted about new benefits across all the portals.  Swell.  Now I have to inject the announcement module across all of the portals. 

I have a real need for this and I am looked through the Dotnetnuke.Ui.Skin...   I see where the roles are checked to determine visibility and options of the panes.  Would it follow in the same logic?

It seems that if I can have a module show up on all the pages in a portal that I could have it show up on all of the pages in all the portals.  (If you could do it within a skin why not with tabs/pages.)  Imagine spaces.msn.com.  You give the end users a limited number of features, modules, control, etc.