Just because you can add as many fields as you want to an object - it doesn't mean you should. The power of a relational database comes in being able to see related objects in the page view - so you don't want to add too many extra fields with lookups in the record detail itself.

If you want to see a lot of different fields from different objects in one place, create a report!

But what do you do you do if, for example, you want to start keeping track of tools that are being used at different occurrences? Do you add fields to keep track of the tools?

NO. To fully leverage the power of a relational database you would create a new object: Tools.

This article details the steps taken by System Admins to enable the Batch Create Functionality for Team Members and Connections.

NOTE: The ability to batch create Team Members and Connections while making it easier to complete these steps have the potential to corrupt or duplicate your data. System Admins should only enable these features for trained users. It is not recommended that you enable this feature for Partner Staff. If desired you can use permission sets to enable it for designated staff and partner staff users.

To learn more about permission sets, see this Salesforce post

When a staff member at a partner staff leaves their position, and no longer should have access to their partner portal, you need to perform a couple of steps to do this.

The Default workflow user's email address is set, by default, as the Sender of all email alerts send through workflows.

It can be defined to be any licensed salesforce user in your organization - and typically is the System Administrator.