permissions errors when reaching out to other databases and servers from within a stored procedure

Be wary of reaching out to other servers or databases within stored procedures. Yesterday I tried to alter a stored procedure and in doing so I got a permissions error telling me I couldn't. I tried to troubleshoot. If you'll imagine that the stored proc was made up of ten hunks of code then I progressively tried removing one after another until I was able to make the alteration. I then tried to add anew the blob of code that was troublesome and found that I could not as it called a table on another server and I merely did not have rights to see the table in question. I had to ask a coworker to fix what I broke.