Is there a way to only grant Admin access to a specific project type?

We have one area, and possibly more later, outside of IT that use Daptiv.  In order for them to create/generate projects from a Project Request they need Admin access.  We would like to be able to only grant Admin access to a specific project type to prevent them from changing anything within other project types.  Is this possible?

We don't currently have the ability to restrict access to project types or templates by role in this way.  One way to address this is by requiring users to create projects from Templates, then have templates corresponding with the project type/department.  Another way is to use the Project Request webforms for creating the Project Request initially, which then "locks" the project type as part of the request.

I'm curious as to why you need to grant admin access to users in order to use project requests?  Any user profile of Project Manager or greater can be configured to create/manage Project Requests.  The only additional permission an Administrator could have is administration of the project request types themselves.

It is more for maintaining project fields.  I misstated earlier.  We have one area outside of IT that is using Daptiv.  Periodically they will need to make changes to their fields.  Sometimes this involves changing the items within a pick list or simply renaming a field.  It would be nice to simply grant them access to the items that they would need to manage.

In this case, I recommend you implement some kind of Daptiv Change Request process.  I have worked with a number of customers who created a DA for this purposes, allowing any user to request updates to the Daptiv environment.  This way, you have one central team (hopefully no more than 2 or 3 people) who are responsible for the general upkeep of the system and can ensure changes are made in line with your current configuration or enterprise requirements.  This also allows administrators to close requests when they're done, which documents what changes were requested by whom and who made the changes.

I've had to work in environments where there is no centralized control, and they can very quickly spiral out of control if too many people have access to administrative functions, no matter how trivial the changes may seem to be.  When you consider the potential impact of changing a single field value for your custom views, executive tab, web forms, and reporting requirements, it's best to make sure any changes go through some kind of formal process so it's documented and fully implemented where appropriate.