anyone have any idea on how to stop “Voyager Workspace” from appearing on the the “New” menu in infoview. 
I have accessed all of the known pdf’s and tried many things but no luck. There is a shinny penny in it for you if you have the answer 
LANFIELD 
(BOB member since 2006-05-18)
I dont have the Voyager option in my environment yet (havent installed all the latest HF yet) but could http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=3317500&sliceId=&dialogID=7558194&stateId=1 0 7560012 help you out?
Perhaps there is a voyager XML file that could have the same effect?
Do let us know! (and send me the penny if it works 8) )
Orange 
(BOB member since 2006-09-18)
well maybe i didnt explain the full issue.
we have licenses for 17 people to create Voyager Docs
we have licenses for everyone to view/refresh/toy with prebuilt voyager docs
for everyone other then the 17 i wanted to remove the option from the “New” menu.
you can reduce the rights for everyone from using the connections for voyager docs and if no available connections appear then the option comes off the menu. but if they dont have access to the connection then they cant run the prebuilt ones they should have access to.
so to be in compliance i need to remove the new option for those that dont have a create license. but the application provides no possible way to be compliant.
LANFIELD 
(BOB member since 2006-05-18)
and sure they don’t have any tool to make sure you are compliant 
I don’t work on Voyager security settings yet but there is no other way than connections to set security? nothing under BOE Applications?
Regards
no nothing under the BOE appications for voyager.
LANFIELD (BOB member since 2006-05-18)
Is it possible to create connections folders?
no. it has its own cmc object just like universe connections and universes. it has no folders for them.
LANFIELD (BOB member since 2006-05-18)
Did you ask OCS how to solve this? sdk could be the solution but BO must provide you a solution!
Regards
Yeah i have a ticket out but no real answer has come back yet. i have notified my rep so they are aware that they have a license that the app cant inforce.
LANFIELD (BOB member since 2006-05-18)
Hi,
Can someone help me to know how can I do to get my users dont see the Voyager toolbar. I guess this is through SDK, but I have no idea where to start. I am using BOEXI 3.1
Thanks a lot!
jasdue.
jasdue (BOB member since 2007-02-07)
This might help. We are preparing to migrate to 3.1 soon and have a nearly “factory installed” CMC to work with for now. We needed to do the opposite- to grant 1 group access to a Voyager connection.
You need to set or take away access rights to the Voyager Connections folder (who knew there was a folder?).
From the Home screen, go to the Voyager Connections. Click on Manage | Top-Level Security | Voyager Connection Folder Rights. A warning dialog box opens, read and click OK. If yours is like ours, you’ll see that the Everyone group has No Access. Or, change it to No Access and add the group you want to give access. We only gave the group we added into this User Security: CommonConnections dialog box View Access. Not sure what else you could or would want to do.
Sandy
Sandy Brotje (BOB member since 2002-07-24)
I found this in the Voyager admin guide (Pg 15-18 )
Voyager offers the flexibility to control which users are able to view or create Voyager workspaces, and also which data they can view. This control is in addition to any inherent data security provided by the OLAP server.
To enable access to data, you must grant Voyager users appropriate rights to the Voyager Connections folder, or to specific connection objects.
By default, the access level for the Everyone group is set to No Access
for the Voyager Connections folder. This setting results in these effects for
Voyager end users (non-administrators):
New Voyager workspaces cannot be created (there is no Voyager
Workspace entry in the InfoView New menu).
End users cannot use any Voyager connections; therefore, any existing
Voyager workspaces will fail to open.
The Voyager Connections page in the Central Management Console is
unavailable.
If you want to allow end users access to specific Voyager connections, but
do not want to make Voyager Workspace available to them in the New
menu in InfoView, grant those users the View access level for those
connections only.
Because rights assigned to a child object override inherited rights, end users
can access Voyager connections if they have been granted the View access
level for individual connection objects, even if their access to the Voyager
Connections folder is set to No Access.
If you grant the View access level for the Voyager Connections folder to
end users, Voyager Workspace is available in the New menu. The end
users then inherit the View access level for the Voyager connections inside
the folder. If you do not want to allow end users access to a specific
connection, you can assign the No Access access level to that connection.
These combinations allow you to control who can and cannot create new
Voyager workspaces and Voyager connections, plus also control who can
view which Voyager-related data.
If you set the access level to “No access”, these users will not see
“Voyager Workspace” in the New menu in InfoView. Users need at least
“View” rights to the Voyager Connections folder to create a Voyager
Workspace.
P34C3 (BOB member since 2005-11-30)